Skip to content

chore: track superpowers artifacts via GitHub epics/issues (CLAUDE.md) #34

Description

@rahlk

Type: chore · Branch:chore/issue-34-track-superpowers-artifacts

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions