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

14
skills/using-superpowers/SKILL.md
View File

@@ -65,9 +65,19 @@ After the user opts in: "Fix this bug" → debugging first, then domain-specific
The skill itself tells you which.
## Local Artifacts
## Project Plan Storage
Generated design specs and implementation plans are local working artifacts. Keep them outside git by default under `.superpowers-lite/`, and ensure that path is ignored via `.git/info/exclude` before writing files.
Generated design specs and implementation plans live under `.superpowers-lite/`.
On first use in a project, if `.superpowers-lite/` does not exist, ask the user whether Superpowers Lite plans/specs should be tracked by git for this project. If `.superpowers-lite/` exists but `.superpowers-lite/config.json` is missing, ask the same question once and create the config. Save the answer in `.superpowers-lite/config.json`:
```json
{
"planGitTracking": "local"
}
```
Use `"tracked"` when the user wants plans/specs in git. Use `"local"` when they should stay local. For later sessions, do not ask again; follow the local config. If the config says `"local"`, ensure `.superpowers-lite/` is listed in `.git/info/exclude` before writing plan/spec files. If it says `"tracked"`, do not add `.superpowers-lite/` to `.git/info/exclude`.
## User Instructions