fjy8018/superpowers-lite
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Refine Superpowers Lite execution workflow

Browse Source
This commit is contained in:
mujing
2026-05-13 15:29:23 +08:00
parent dd2eb8b351
commit 883f225584
8 changed files with 115 additions and 117 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
skills/brainstorming/SKILL.md
View File

@@ -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 `.superpowers-lite/specs/YYYY-MM-DD-<topic>-design.md` and keep it out of git
6. **Write design doc** — save to `.superpowers-lite/specs/YYYY-MM-DD-<topic>-design.md` using the project plan storage config
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
@@ -108,11 +108,15 @@ digraph brainstorming {
**Documentation:**
- Before writing files, ensure `.superpowers-lite/` is listed in `.git/info/exclude` when the project is a git repository
- Before writing files, check whether `.superpowers-lite/` exists
- If it does not exist, ask whether Superpowers Lite plans/specs should be tracked by git for this project, then create `.superpowers-lite/config.json` with `planGitTracking` set to `"tracked"` or `"local"`
- If `.superpowers-lite/` exists but `.superpowers-lite/config.json` is missing, ask the same question once and create the config
- If `.superpowers-lite/config.json` already exists, follow it without asking again
- If `planGitTracking` is `"local"`, ensure `.superpowers-lite/` is listed in `.git/info/exclude`; if it is `"tracked"`, do not exclude it
- Write the validated design (spec) to `.superpowers-lite/specs/YYYY-MM-DD-<topic>-design.md`
- (User preferences for spec location override this default)
- Use elements-of-style:writing-clearly-and-concisely skill if available
- Do not commit generated design documents unless the user explicitly asks
- Commit or leave generated design documents uncommitted according to the user's normal workflow and the project plan storage config
**Spec Self-Review:**
After writing the spec document, look at it with fresh eyes:
@@ -127,7 +131,7 @@ Fix any issues inline. No need to re-review — just fix and move on.
**User Review Gate:**
After the spec review loop passes, ask the user to review the written spec before proceeding:
> "Spec written to `<path>` as a local, untracked artifact. Please review it and let me know if you want to make any changes before we start writing out the implementation plan."
> "Spec written to `<path>`. Please review it and let me know if you want to make any changes before we start writing out the implementation plan."
Wait for the user's response. If they request changes, make them and re-run the spec review loop. Only proceed once the user approves.