Collaborative Walkthrough
Use this skill as the human sign-off gate for DOCS/PROJECTS/in-review/ streams before moving work to completed/.
First Checks
- Locate
DOCS/PROJECTS/in-review/. - Read
AGENTS.md,ROADMAP.md,CHANGELOG.md, andDOCS/PROJECTS/README.mdwhen present. - Enumerate in-review project docs.
- Include child projects and parent rollups when
parentProjectorprogramTrackis present.
If no in-review/ folder exists, offer to run $context-layer-scaffold.
Required Behavior
- Never auto-transition projects to
completed. - Present evidence-backed readiness findings first.
- Ask concise sign-off questions.
- Call out missing evidence, blockers, unresolved
MAGGIE TODO:items, and policy decisions. - Only transition streams after explicit user approval.
- If approvals are partial, transition only approved streams.
Readiness Classes
ready-for-signoff: no unresolved blockers, no critical unanswered decisions, evidence is linked.needs-user-input: Maggie or another human must decide, approve, test, or provide input.follow-up-needed: technical, documentation, evidence, or verification gaps should be addressed first.
Approval Actions
For each approved project:
- Generate an ET timestamp with
node scripts/docs/timestamp-et.mjs --json. - Add a completion checkpoint.
- Set frontmatter
status: completed. - Move the file to
DOCS/PROJECTS/completed/. - Update
ROADMAP.mdandCHANGELOG.md. - Regenerate the project dashboard.
- Run docs checks when available.
Output Contract
Return sections in this order:
Walkthrough StatusProject Readiness MatrixWhat Needs Your InputRecommended Actions Before Sign-OffSign-Off Questions
For each project include id/title, readiness class, and 1-3 evidence bullets with file references.