plan-code

Builds an implementation-ready task plan from an approved specification within an active work stream.

4|1|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/alvis/.agents --skill plan-code-alvis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-code
Source: https://github.com/alvis/.agents/tree/main/plugins/specification/skills/plan-code
Command: npx skills add https://github.com/alvis/.agents --skill plan-code-alvis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved specification into an executable implementation plan often produces vague task lists, hidden decisions, and plans that drift from the approved spec. This Skill converts an approved specification into a decision-complete blueprint with stable task IDs, explicit dependencies, and verifiable acceptance mappings stored in the active work stream. ## Core Features & Use Cases - Decision Surface Resolution: Classifies data, interface, security, and integration decisions as resolved, assumed, deferred, or blocking before any implementation detail is written. - Stable Task Registry: Assigns globally unique mnemonic task IDs (e.g., LFE, LFE01) with explicit dependency edges, atomic executable leaves, and acceptance criteria mappings in the root state.md registry. - Specification Authority Checks: Verifies the approved specification content against provenance and source drift before planning, routing stale or unapproved specs back through the specification workflow. - Use Case: After a feature specification is approved, invoke this Skill to produce a reviewed task DAG with per-task targets and acceptance mappings, ready for the implementation skills to execute without re-deriving decisions. ## Quick Start Ask the agent to plan the implementation for the approved specification in the current work stream using plan-code.

Frequently Asked Questions about plan-code

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

FAQPage Schema
How do I turn an approved specification into an implementation plan?

Invoke plan-code with the active work stream containing the approved specification. It resolves the decision surface, assigns stable mnemonic task IDs with dependencies, and writes a reconciliation payload for the root state.md task registry.

What happens if the specification changed after approval?

The skill re-verifies the specification content against its recorded provenance before planning. If the content differs from the approved version or the source drifted, it returns ready_for_specification and routes back through spec-code instead of planning from stale intent.

How are task IDs and dependencies structured in the plan?

Each top-level task gets a unique three-letter ID like LFE, with executable children suffixed 01-99 such as LFE01. Dependencies are recorded explicitly by full ID, with cross-parent child edges, cycles, and dangling edges prohibited.

Does plan-code edit the root state.md or goal.md files directly?

No. The skill never edits main-agent-owned files like state.md, goal.md, or the journal. It returns a reconciliation payload containing the task registry, plan_source pointer, and status deltas for the main agent to apply.

When should I not use plan-code for planning work?

Do not use it without an approved specification reachable from the active work state, since missing approval returns ready_for_spec_approval. It also does not implement source code or create independent root planning artifacts outside the work stream.