code-plan

Generates a feature implementation plan by orchestrating planner and skeptic subagents.

4|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/alexeyshishin/as-skill --skill code-plan-alexeyshishin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-plan
Source: https://github.com/alexeyshishin/as-skill/tree/main/domains/code/skills/code-plan
Command: npx skills add https://github.com/alexeyshishin/as-skill --skill code-plan-alexeyshishin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into coding a multi-file feature without a plan leads to missed edge cases, unclear scope, and rework. This Skill designs the feature before any code is written by having two subagents argue over the approach and producing a reviewed plan. ## Core Features & Use Cases - Dual-subagent design: Spawns a planner subagent to draft the plan and a skeptic subagent to attack it, then merges their outputs. - Memory Bank awareness: Reads .memory-bank/index.md for project context so plans reflect existing architecture. - Structured plan output: Writes swarm-report/<slug>-plan.md with acceptance criteria, affected files, tests, blockers, and assumptions. - Use Case: Before implementing "add OAuth login to the API", run the Skill to get a plan with acceptance criteria that /code-review can later verify, plus a list of unresolved blockers for human decision. ## Quick Start Ask the AI to run /code-plan with a one-sentence description of the feature you want to build, such as "/code-plan add rate limiting to the public API endpoints".

Frequently Asked Questions about code-plan

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

FAQPage Schema
How do I plan a feature before writing code with AI agents?

Invoke /code-plan with a one-sentence feature description. It spawns a planner subagent to draft the plan and a skeptic subagent to attack it, then merges their outputs into a plan file in swarm-report/ with acceptance criteria and blockers.

When should I use code-plan versus going straight to code-build?

Use code-plan for any feature touching two or more files or with unclear scope. Skip it for typos and one-line fixes, where the planning overhead adds no value.

Does code-plan write or modify any source code?

No. The Skill only orchestrates planning subagents and writes a markdown plan to swarm-report/. It never edits code; implementation happens later in the code-build step.

What happens if there is no Memory Bank in the project?

The Skill notifies you that no Memory Bank was found and continues planning based only on your feature description. The plan will lack project-specific architectural context.

What are blockers in the generated plan?

Blockers are unresolved HIGH-severity concerns raised by the skeptic subagent that the orchestrator could not settle. They are listed for a human to decide before proceeding to code-build.