plan

Generates a feature architecture plan with charter validation, review panel, and operator runbook.

150|10|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/swingerman/engineer --skill plan-swingerman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/swingerman/engineer/tree/main/engineer/skills/plan
Command: npx skills add https://github.com/swingerman/engineer --skill plan-swingerman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning acceptance criteria and specs into a sound architecture is where AI-assisted development most often goes wrong — plans rest on false premises, cross-track interfaces are left ambiguous, and infrastructure steps get lost. This Skill produces a validated architecture plan (Checkpoint 4 of the DAE pipeline) with human approval gates, charter compliance checks, and a review panel before any code is written. ## Core Features & Use Cases - Architecture proposal with human gate: Drafts components, data flow, coupling, and pinned cross-track interface contracts, grounded in the actual codebase via LSP lookups, then iterates with the human until confirmed. - Charter Check and review panel: Validates the plan against the project CHARTER.md with a compliance table and amendment ADRs, then dispatches an adviser + advocate review panel whose findings are recorded in the handoff. - Runbook generation: When the plan touches provisioning, secrets, DNS, or console-only steps, it writes a runbook.md with per-step human/agent ownership and AC-blocking gate enforcement. - Use Case: After defining ACs and Given/When/Then specs for a new staging-environment feature, invoke the planner to produce plan.md with architecture, phasing, test strategy, and a runbook for the GCP provisioning steps — all approved before implementation begins. ## Quick Start Ask the agent to plan the implementation for the current feature so it produces plan.md with the architecture, charter check, and test strategy.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create an architecture plan from acceptance criteria before coding?▼

Run the plan checkpoint after ACs and specs exist: it loads feature.md, acs.md, and spec.md, drafts an Architecture section grounded in the actual codebase, and iterates with you until confirmed. The output is plan.md with phasing, test strategy, and a charter compliance check.

What is a charter check in spec-driven development?▼

A charter check validates the plan against the project's CHARTER.md rules, producing a compliance table with one row per rule plus an Amendments section. A plan cannot finish with an unresolved deviation — it must either include an amendment ADR or stop and request a human decision.

Can I plan a feature without a formal spec file?▼

Yes, but the skill warns that planning should follow spec formalization. You may override and plan from acs.md alone, and the skipped step is flagged in the handoff so the gap stays visible.

When does the plan skill generate a runbook for infrastructure steps?▼

A runbook.md is generated only when the plan touches provisioning, secrets, DNS, console-only configuration, or third-party service setup. Each step gets human or agent ownership, and deploy-related acceptance criteria cannot claim green until blocking steps are completed.

Why does the plan workflow stop before drafting the full plan?▼

By default the agent drafts only the Architecture section and waits for human confirmation, since architecture is a human decision. Under bundled or auto gate profiles at medium or high autonomy, it drafts everything in one pass and approval happens at the bundled front gate.