refactor(skills): move orchestration state files to docs/superpowers/states/#2
Merged
Merged
Conversation
The orchestration state file lived inside docs/superpowers/plans/, co-located with the plan. Give it its own docs/superpowers/states/ directory so state is a distinct namespace from the plan it tracks. Lifecycle is unchanged: state stays scratch, deleted in the orchestrator's last commit when the feature ships. Only the path and the "beside the plan" wording change. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The orchestration state file — the resume-from artifact for a feature in flight — lived at
docs/superpowers/plans/<date>-<slug>-state.md, mixed in with the plan it tracks. This gives it its own home at a siblingdocs/superpowers/states/directory, distinct fromspecs/andplans/, while keeping the same scratch lifecycle as the plan (deleted once the feature ships). Pure path/convention change across the skills, README, and the project-CLAUDE template; no behavioural logic changes.Changes
docs/superpowers/states/<date>-<slug>-state.md(was underdocs/superpowers/plans/).planning-a-featureStep 8 writes the new path;developing-a-feature,fanning-out-with-worktrees, andreviewing-feature-progressread it from there.docs/superpowers/states/directory alongsidespecs/andplans/.templates/project-CLAUDE.mdnotes state files live instates/and share the plan's scratch lifecycle.Testing
Documentation / path-convention change only; no executable code. Verified every state-file reference across the plugin was moved:
git grepforplans/…-state.mdreturns nothing on the branch, and all six touched files (four skills, README, template) carry the newstates/path consistently.