Is your feature request related to a problem? Please describe.
Type: chore · Branch: chore/issue-34-track-superpowers-artifacts
Describe the solution you'd like
Not stated in the original issue.
Describe alternatives you've considered
Not stated in the original issue.
Additional context
What
Codify how Superpowers workflow artifacts are tracked in git. docs/superpowers/** (brainstorming specs, writing-plans plans) is globally gitignored, so rather than committing those files we track the work in GitHub:
- Spec → epic issue, plan → one issue per work item, each issue →
<type>/issue-XXX-<short-title> branch → one PR against main that closes it.
Change (already in the working tree)
CLAUDE.md: tightened rule 3's branch naming and added a "Tracking work — specs → epics, plans → issues" section. AGENTS.md inherits it via the symlink.
This convention is already in use by epic #26 and its children (#27–#33).
Acceptance
- The
CLAUDE.md / AGENTS.md change lands via this issue's branch + PR against main.
Is your feature request related to a problem? Please describe.
Type: chore · Branch:
chore/issue-34-track-superpowers-artifactsDescribe the solution you'd like
Not stated in the original issue.
Describe alternatives you've considered
Not stated in the original issue.
Additional context
What
Codify how Superpowers workflow artifacts are tracked in git.
docs/superpowers/**(brainstorming specs, writing-plans plans) is globally gitignored, so rather than committing those files we track the work in GitHub:<type>/issue-XXX-<short-title>branch → one PR againstmainthat closes it.Change (already in the working tree)
CLAUDE.md: tightened rule 3's branch naming and added a "Tracking work — specs → epics, plans → issues" section.AGENTS.mdinherits it via the symlink.This convention is already in use by epic #26 and its children (#27–#33).
Acceptance
CLAUDE.md/AGENTS.mdchange lands via this issue's branch + PR againstmain.