From 0b36755bca00620f0c768f7b21cf90e0f3b56376 Mon Sep 17 00:00:00 2001 From: untko Date: Fri, 24 Jul 2026 15:49:06 +0700 Subject: [PATCH] docs(skills): brainstorming should propose commit instead of committing directly --- skills/brainstorming/SKILL.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/skills/brainstorming/SKILL.md b/skills/brainstorming/SKILL.md index 789c3a1990..458bd3c13a 100644 --- a/skills/brainstorming/SKILL.md +++ b/skills/brainstorming/SKILL.md @@ -26,7 +26,7 @@ You MUST create a task for each of these items and complete them in order: 3. **Ask clarifying questions** — one at a time, understand purpose/constraints/success criteria 4. **Propose 2-3 approaches** — with trade-offs and your recommendation 5. **Present design** — in sections scaled to their complexity, get user approval after each section -6. **Write design doc** — save to `docs/superpowers/specs/YYYY-MM-DD--design.md` and commit +6. **Write design doc** — save to `docs/superpowers/specs/YYYY-MM-DD--design.md` and commit (propose the commit first if in an interactive human session) 7. **Spec self-review** — quick inline check for placeholders, contradictions, ambiguity, scope (see below) 8. **User reviews written spec** — ask user to review the spec file before proceeding 9. **Transition to implementation** — invoke writing-plans skill to create implementation plan @@ -107,7 +107,7 @@ digraph brainstorming { - Write the validated design (spec) to `docs/superpowers/specs/YYYY-MM-DD--design.md` - (User preferences for spec location override this default) - Use elements-of-style:writing-clearly-and-concisely skill if available -- Commit the design document to git +- Propose the git commit command to stage and commit the spec document if in an interactive session with a human partner; commit directly if running autonomously (e.g., as a background subagent) or inside an isolated task worktree **Spec Self-Review:** After writing the spec document, look at it with fresh eyes: