plan

Generate external specs and execution plans stored in docs directories.

36|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/cagdotin/agents --skill plan-cagdotin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/cagdotin/agents/tree/main/skills/engineering/plan
Command: npx skills add https://github.com/cagdotin/agents --skill plan-cagdotin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It enables teams to formalize tasks by generating a formal spec and an execution plan, ensuring decisions are captured and accessible in docs/specs/ and docs/exec-plans/active/.

Core Features & Use Cases

  • Spec generation: creates an external specification detailing goals, constraints, and decisions.
  • Execution planning: produces a concrete, step-by-step execution plan aligned to PLAN.md structure.
  • Living artifacts: keeps specs and plans up-to-date across sessions and projects, enabling easy handoff and auditing.

Quick Start

Run the plan skill on a new task to generate a spec under docs/specs/ and an execution plan under docs/exec-plans/active/.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I auto-create specs and execution plans for software tasks?

You can auto-create specs and execution plans by running the plan skill on a task. It generates a formal specification and a step-by-step execution plan, storing them in docs/specs/ and docs/exec-plans/active/.

What is the best way to maintain living implementation artifacts across project sessions?

Living implementation artifacts are maintained by keeping the generated specs and execution plans in docs/specs/ and docs/exec-plans/active/. This ensures decisions are captured and accessible for easy handoff and auditing across sessions.

How do I generate a structured execution plan aligned to PLAN.md structure?

To generate a structured execution plan aligned to PLAN.md structure, run the plan skill on your task. It produces a concrete, step-by-step execution plan detailing the required actions and decisions.

Does the plan skill require existing documentation to generate a formal spec?

No existing documentation is required to generate a formal spec. The plan skill ensures self-discovery of context before asking questions, automatically creating the external specification detailing goals, constraints, and decisions.

Can I use this planning approach for collaborative or delegated software engineering tasks?

Yes, you can use this planning approach for collaborative or delegated software engineering tasks. The skill applies to tasks requiring structured planning and traceable decisions across both modes, formalizing the handoff process.