Create living plan documents with goals, scope, milestones, and next-slice contracts.
npx skills add https://github.com/scripness/skills --skill plan-scripness
Please help me install this Agent Skill. Skill: plan Source: https://github.com/scripness/skills/tree/main/src/plan Command: npx skills add https://github.com/scripness/skills --skill plan-scripness
Organize work that requires durable state across sessions into living plan documents, enabling safe handoffs and reproducible execution loops.
Create a new plans/YYYY-MM-DD-short-task-slug.md describing a bounded, resumable plan for the task.
High-intent search queries and answers about installing and using this skill.
To create a durable task plan, you generate a living plan document in the plans/ directory that defines goals, scope, milestones, and an explicit next-slice contract. This ensures execution state persists safely across sessions and restarts.
Resuming multi-milestone tasks requires a resumable plan document that syncs repo truth like AGENTS.md and tests with executable truth. This allows new sessions to pick up execution and verification exactly where the previous session left off.
Living plan documents manage blockers and handoffs by maintaining a transparent decision log alongside milestone tracking. This durable state captures what happened, what remains, and what the next slice of work is for safe reproducible execution.
You need a structured plan document when work spans multi-milestone tasks that may experience interruptions or require handoffs. It enforces done conditions and spec-test alignment to guide execute and verify phases across bounded milestones.
Yes, the plan structure syncs repository truth such as AGENTS.md, specs, and tests with executable truth. This alignment keeps slice-level specs and tests verifiable when you resume execution from the plan in a new session.
When defining next-slice contracts, avoid creating unbounded milestones without explicit done conditions. The plan structure requires slice-level specs and tests to stay aligned, so missing these conditions breaks execution and verification continuity across sessions.
rocky2431Suggest next-step commands based on project state signals.
levnikolaevichOrchestrate end-to-end Story execution with task delegation and quality gates.
nsheapsSyncs global Claude directory todos and plans into the project's .claude directory.
djankiesGuide high-risk changes through plan, validate, execute, and verify phases.
