skills.rest
Emmanuel-R8
Emmanuel-R8COMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

Generates detailed implementation plans with bite-sized TDD tasks from specs.

1|Updated Feb 18, 2026
Search Tags:#planning#tdd#pytest#task breakdown#implementation plan#spec#git commits
One-click install
npx skills add https://github.com/Emmanuel-R8/aikos --skill writing-plans-emmanuel-r8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Emmanuel-R8/aikos/tree/main/.cursor/skills/writing-plans
Command: npx skills add https://github.com/Emmanuel-R8/aikos --skill writing-plans-emmanuel-r8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineers often start coding multi-step features without a clear roadmap, leading to missed requirements, inconsistent testing, and lost context. This Skill turns a spec or requirements document into a comprehensive implementation plan that any engineer can follow, even with zero codebase context. ## Core Features & Use Cases - Bite-Sized Task Breakdown: Splits work into 2-5 minute steps following TDD: write failing test, verify failure, implement, verify pass, commit. - Exact File and Command References: Every task lists exact file paths to create or modify, complete code snippets, and test commands with expected output. - Execution Handoff: After saving the plan to docs/plans/YYYY-MM-DD-<feature-name>.md, it offers subagent-driven or parallel-session execution options. - Use Case: Given a feature spec for a new API endpoint, produce a plan document where each task includes the failing test code, the minimal implementation, the pytest command, and the git commit step. ## Quick Start Ask the AI to use the writing-plans skill to create an implementation plan from your feature spec before writing any code.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I write an implementation plan before coding a feature?▼

Provide your spec or requirements and invoke the writing-plans skill. It produces a plan document with a goal, architecture summary, tech stack, and numbered tasks, each containing exact file paths, test code, implementation code, and commit steps.

How to break a coding task into TDD steps?▼

Each task is split into five steps: write the failing test, run it to confirm failure, write the minimal implementation, run the test to confirm it passes, then commit. Each step is designed to take 2-5 minutes.

Where are implementation plans saved?▼

Plans are saved as markdown files under docs/plans/ using the naming pattern YYYY-MM-DD-<feature-name>.md. The skill is intended to run in a dedicated worktree created by a brainstorming skill.

Can I execute the plan automatically after writing it?▼

Yes. After saving, the skill offers two execution modes: subagent-driven execution in the current session with a fresh subagent per task, or a parallel session using the executing-plans skill for batch execution with checkpoints.

When should I not use a detailed implementation plan?▼

Skip the plan for trivial single-step changes or exploratory spikes where requirements are unclear. The skill is designed for multi-step tasks with a defined spec, following YAGNI to avoid over-planning.

Related Skills

Explore More Software Engineering Skills→
lapaixkemsdortshlee-svglapaixkemsdortshlee-svg

brainstorming

Shape vague product ideas into clear design directions before implementation.

Community
Advanced
royhenengelroyhenengel

subagent-driven-development

Executes implementation plans by dispatching subagents for tasks with code review between them.

Community
Advanced
tony30552001tony30552001

plan-eng-review

Review architecture, data flow, diagrams, edge cases, test coverage, and performance.

Community
Advanced
busboom-software-studiobusboom-software-studio
1

oop

Apply small targeted changes directly on master with test suite runs.

Official
Intermediate