plan

Decomposes an active goal contract into a phased, TDD-stepped plan folder with a live tracking ledger.

1|1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/Navdeepgambhir9023/nav --skill plan-navdeepgambhir9023
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Navdeepgambhir9023/nav/tree/main/skills/plan
Command: npx skills add https://github.com/Navdeepgambhir9023/nav --skill plan-navdeepgambhir9023

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml.

What problem does it solve? Turning a signed-off goal contract into executable work is where most agent workflows break down: criteria go uncovered, dependencies form cycles, and executors receive vague instructions they cannot verify. This Skill converts an ACTIVE contract into a structured plan folder that a dispatch loop can execute and resume deterministically. ## Core Features & Use Cases - Contract-to-DAG decomposition: Breaks a contract into tasks with declared produces/consumes/scope_paths, verifies the dependency graph is cycle-free, and guarantees every mandatory acceptance criterion maps to at least one task. - Phase files with TDD discipline: Writes per-phase step files (failing test → implement → verify → commit → update tracking), with a non-TDD step shape for docs, config, and KB tasks. - Live tracking ledger: Generates tracking.md as a strict 3-level checklist that the execution loop reads for restart-resume after failures. - Legacy migration scripts: Ships shell scripts that convert old single-file plan.md documents into the new schema-2 plan folder shape, idempotently and reversibly. - Use Case: After defining a goal contract for a feature (e.g., migrate a component library), run the planner to produce a 5-phase plan folder where each task has verifiable acceptance, disjoint scope paths for parallel waves, and a drift check before handoff. ## Quick Start Ask the agent to decompose the currently active goal contract into a phased plan folder with TDD steps and a tracking ledger, then review the generated overview before handing off to the execution loop.

Frequently Asked Questions about plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a goal contract into an executable task plan?

Run the plan skill after the contract reaches ACTIVE status. It decomposes the contract into tasks with produces/consumes dependencies, groups them into phase files with TDD steps, and writes a tracking.md ledger the execution loop reads for dispatch and resume.

How do I migrate a legacy single-file plan.md to the plan folder format?

Run migrate-single-file-plan.sh with the goal id to convert one plan, or migrate-all-single-file-plans.sh to batch-convert every goal under .loop/goals. Both are idempotent and preserve the original as plan.md.legacy for reversibility.

What happens if a mandatory acceptance criterion is not covered by any task?

The plan is invalid and the skill returns to the goal stage for recontracting instead of proceeding. Every mandatory criterion in contract.json must appear in at least one task's covers_criteria list before handoff.

Can tasks run in parallel during plan execution?

Yes, tasks marked parallelizable can share a wave, but only when their scope_paths are pairwise disjoint. The planner verifies this during decomposition so the wave analyzer can schedule them safely.

When should the planning step be skipped?

Skip only for prototype-mode goals with three or fewer acceptance criteria where the owner approved inline execution at intake. In that case the loop inlines a minimal single-phase plan folder instead of running full decomposition.

Why does the plan handoff fail with a drift check error?

The drift check (exit code 2) means the contract and plan folder diverged or an unanticipated scope-path edit occurred. The skill halts and offers recontract, plan amendment, or upstream rollback rather than handing off a drifting plan.