john/claude-engineering-plugin
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

refactor: Make Proof sharing optional in brainstorm and plan workflows

Browse Source 
- Remove automatic Proof upload from /workflows:brainstorm and /workflows:plan
- Add "Share to Proof" as an explicit menu option in each workflow's handoff step
- Default behavior is unchanged: documents are saved to MD files only
- Users can opt in to Proof sharing when they want collaborative review

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Kieran Klaassen
2026-03-01 15:01:11 -08:00
parent 3b4e0ae11f
commit 6b46fb2ccf
3 changed files with 34 additions and 57 deletions
Download Patch File Download Diff File Expand all files Collapse all files

45
plugins/compound-engineering/commands/workflows/brainstorm.md
View File

@@ -89,8 +89,24 @@ Use **AskUserQuestion tool** to present next steps:
**Options:**
1. **Review and refine** - Improve the document through structured self-review
2. **Proceed to planning** - Run `/workflows:plan` (will auto-detect this brainstorm)
3. **Ask more questions** - I have more questions to clarify before moving on
4. **Done for now** - Return later
3. **Share to Proof** - Upload to Proof for collaborative review and sharing
4. **Ask more questions** - I have more questions to clarify before moving on
5. **Done for now** - Return later
**If user selects "Share to Proof":**
```bash
CONTENT=$(cat docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md)
TITLE="Brainstorm: <topic title>"
RESPONSE=$(curl -s -X POST https://www.proofeditor.ai/share/markdown \
-H "Content-Type: application/json" \
-d "$(jq -n --arg title "$TITLE" --arg markdown "$CONTENT" --arg by "ai:compound" '{title: $title, markdown: $markdown, by: $by}')")
PROOF_URL=$(echo "$RESPONSE" | jq -r '.tokenUrl')
```
Display the URL prominently: `View & collaborate in Proof: <PROOF_URL>`
If the curl fails, skip silently. Then return to the Phase 4 options.
**If user selects "Ask more questions":** YOU (Claude) return to Phase 1.2 (Collaborative Dialogue) and continue asking the USER questions one at a time to further refine the design. The user wants YOU to probe deeper - ask about edge cases, constraints, preferences, or areas not yet explored. Continue until the user is satisfied, then return to Phase 4.
@@ -119,31 +135,6 @@ Key decisions:
Next: Run `/workflows:plan` when ready to implement.
```
### Share to Proof
After writing the brainstorm document, upload it to Proof for collaborative review:
```bash
# Read the brainstorm file content
CONTENT=$(cat docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md)
TITLE="Brainstorm: <topic title>"
# Upload to Proof
RESPONSE=$(curl -s -X POST https://www.proofeditor.ai/share/markdown \
-H "Content-Type: application/json" \
-d "$(jq -n --arg title "$TITLE" --arg markdown "$CONTENT" --arg by "ai:compound" '{title: $title, markdown: $markdown, by: $by}')")
PROOF_URL=$(echo "$RESPONSE" | jq -r '.tokenUrl')
```
Display the Proof URL prominently:
```
View & collaborate in Proof: <PROOF_URL>
```
If the curl fails (network error, non-JSON response), skip silently and continue — Proof sharing is optional.
## Important Guidelines
- **Stay focused on WHAT, not HOW** - Implementation details belong in the plan