maggielerman Project Lifecycle
Use this skill for repo-native project state under DOCS/PROJECTS/.
First Checks
- Locate
DOCS/PROJECTS/. - Read
DOCS/PROJECTS/README.md. - Identify the project doc by number, title, filename, or current work context.
If the repo is not scaffolded, offer to run $context-layer-scaffold.
Lifecycle Lanes
active/: implementation in progressin-review/: implementation complete, waiting for walkthrough/sign-offblocked/: waiting on user decision, permission, access, manual input, or external dependencycompleted/: delivered after walkthrough/sign-offbacklog/: queuedstale/: paused or deprecated
Transition Rules
- Move to
in-review/only after end-to-end execution is done. - Move to
blocked/when progress requires Maggie or an external dependency. - Move to
completed/only after walkthrough/sign-off. - Update frontmatter
statusto match the lifecycle folder. - Add a timestamped checkpoint for every lifecycle move.
- Reference project numbers in roadmap/changelog entries when the transition matters outside the project doc.
Parent And Child Projects
Use projectType, parentProject, and programTrack frontmatter to preserve hierarchy. Child projects may move independently through lifecycle lanes.