skills.rest
ryanportfolio
ryanportfolioCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

Generates structured implementation plans from specs before writing code.

Updated Aug 30, 2026
Search Tags:#workflow#planning#implementation plan#task decomposition#spec#subagent#plan review
One-click install
npx skills add https://github.com/ryanportfolio/threejs-interview-test --skill writing-plans-ryanportfolio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/ryanportfolio/threejs-interview-test/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/ryanportfolio/threejs-interview-test --skill writing-plans-ryanportfolio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a spec or requirements document into an actionable, multi-step implementation plan is error-prone when done ad hoc, often leading to missed requirements, vague tasks, or plans that stall engineers mid-implementation. ## Core Features & Use Cases - Spec-to-Plan Workflow: Reads a spec or requirements document and produces a decomposed, step-by-step implementation plan before any code is touched. - Independent Plan Review: Dispatches a plan document reviewer subagent that checks completeness, spec alignment, task decomposition, and buildability, flagging only issues that would cause real implementation problems. - Use Case: Given a feature spec for a new API endpoint, produce a written plan with clearly bounded tasks, then have it independently reviewed against the spec to catch missing requirements or placeholder content before implementation begins. ## Quick Start Ask the agent to write an implementation plan from your spec file and have the plan reviewed against the spec before coding.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn a spec into an implementation plan with an AI agent?▼

Provide the spec or requirements file and invoke the writing-plans workflow before touching code. It decomposes the spec into bounded, actionable tasks and writes a plan document that an engineer can follow directly.

How to review an implementation plan for completeness?▼

Dispatch the plan document reviewer subagent with the plan file path and spec file path. It checks completeness, spec alignment, task decomposition, and buildability, returning a status of Approved or Issues Found with specific task-level findings.

What does the plan reviewer flag as a real issue?▼

The reviewer flags only problems that would cause real implementation trouble: missing spec requirements, contradictory steps, placeholder content, TODOs, or tasks too vague to act on. Minor wording and stylistic preferences are explicitly excluded.

When should I write a plan instead of coding directly?▼

Use this workflow whenever you have a spec or requirements for a multi-step task, before touching code. It is most valuable when tasks span multiple components or when missing a requirement would be costly to discover late.

Can the plan reviewer replace independent review with self-review?▼

No. The skill explicitly requires confirming that the session exposes the required multi-agent tools before dispatching review steps, and instructs not to replace independent review with self-review.

Related Skills

Explore More Software Engineering Skills→
LeonardoDiasRRLeonardoDiasRR

writing-specs

Create structured software feature specifications with templates for requirements and acceptance criteria.

Community
Intermediate
wellcrafted-devwellcrafted-dev
35

spec-execution

Execute specification documents through planned waves of parallel and sequential changes.

Official
Advanced
ArcadeAIArcadeAI

brainstorming

Refine rough ideas into validated specs through phased design dialogue.

Official
Intermediate
KentoShimizuKentoShimizu
7

testing-tdd

Automate test-driven development workflows with failing-test-first feedback loops.

Community
Intermediate