writing-plans

Generate structured implementation plans mapping tasks, files, tests, and documentation to a feature.

19|4|Updated Feb 1, 2026

Search Tags:#planning #documentation #TDD #software-engineering #plan-execution #task-breakdown #feature-implementation

Ready to run

npx skills add https://github.com/jarredkenny/agency-ai --skill writing-plans-jarredkenny

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/jarredkenny/agency-ai/tree/main/roles/orchestrator/skills/writing-plans
Command: npx skills add https://github.com/jarredkenny/agency-ai --skill writing-plans-jarredkenny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to convert feature ideas into a repeatable, auditable plan that specifies the files to touch, tests to write, docs to update, and a clear path to delivery. The writing-plans skill generates structured implementation plans that capture scope, tasks, and checkpoints.

Core Features & Use Cases

Plan generation: produces a complete, task-level outline with exact file paths, tests, and documentation steps.
Task granularity: breaks work into bite-sized steps suitable for quick iterations and frequent commits.
Documentation & traceability: saves plans to docs/plans/YYYY-MM-DD-<feature-name>.md with a consistent header and structure for easy review and reuse.
Execution handoff: provides a clear plan document that can be used by developers or subagents to implement the feature.

Quick Start

Use the writing-plans skill to create an implementation plan for a feature named <feature-name>. The plan will be saved to docs/plans/YYYY-MM-DD-<feature-name>.md.

Frequently Asked Questions about writing-plans

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

FAQPage Schema

How do I break down a software feature idea into an executable implementation plan?▼

To create an implementation plan, you define a feature and generate a task-level outline mapping exact file paths, tests, and documentation steps. This structured plan breaks work into bite-sized steps suitable for quick iterations and frequent commits.

What is included in a structured software implementation plan for task breakdown?▼

A structured implementation plan includes a Plan Document Header, task-level steps with exact file paths, tests to write, and documentation updates. It enforces a consistent format and saves to a specific location to ensure traceability and reusability.

How do I ensure traceability for feature implementation plans across my team?▼

You ensure traceability by saving implementation plans to a consistent file path like docs/plans/YYYY-MM-DD-<feature-name>.md. This consistent header and structure makes plans easy to review, audit, and reuse across the software engineering team.

Can I use a generated implementation plan for execution handoff to subagents?▼

Yes, the generated implementation plan provides a clear document for execution handoff. Developers or subagents can use the task-level outline with mapped files, tests, and documentation steps to directly implement the feature.

What's the best way to document tests and file changes before writing code?▼

The best way is generating a structured implementation plan that maps exact file paths, tests, and documentation steps before coding begins. This approach supports TDD workflows and ensures all code, tests, and release artifacts are planned for repeatable delivery.