writing-plans

Convert feature specifications into executable implementation plans with tasks and acceptance criteria.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/boomNDS/soop-discoard-bot --skill writing-plans-boomnds
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/boomNDS/soop-discoard-bot/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/boomNDS/soop-discoard-bot --skill writing-plans-boomnds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert a feature spec or requirements into a complete, auditable implementation plan that an engineer can execute without prior knowledge of the codebase. It emphasizes clarity, scope, and a repeatable process to reduce ambiguity and miscommunication.

Core Features & Use Cases

  • Comprehensive planning: Generates end-to-end implementation plans covering files to touch, tests to write, docs to check, and commit history.
  • Structured task breakdown: Breaks work into bite-sized steps with clear goals, dependencies, and acceptance criteria.
  • Documentation and testing guidance: Includes notes on required docs, tests, and verification methods to ensure traceability.
  • Execution handoff guidance: Provides a plan header and a ready-to-run plan document framework.
  • Use case: When starting a new feature with a vague spec, this skill outputs a plan to guide implementation.

Quick Start

Announce and create a dedicated worktree for planning, then save the plan to docs/plans/YYYY-MM-DD-<feature-name>.md and follow the bite-sized tasks to implement, test, and document.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I convert a feature spec into an implementation plan?

To convert a feature spec into an implementation plan, you input the specification to generate a standardized plan header, stepwise tasks, code references, and clear acceptance criteria for engineering execution.

What is task breakdown in software engineering workflows?

Task breakdown in software engineering workflows is the process of dividing a feature specification into bite-sized, executable steps with clear goals, dependencies, and acceptance criteria to guide delivery.

How do I create an executable plan for developers without codebase context?

You can create an executable plan for developers lacking prior context by generating a comprehensive document detailing files to touch, tests to write, docs to check, and commit history.

Does this implementation planning skill include TDD guidance?

Yes, implementation planning includes TDD guidance by providing specific notes on required tests and verification methods to ensure traceability throughout the development workflow.

What is the best way to structure implementation plans for new features?

The best way to structure implementation plans for new features is using a standardized plan header and a ready-to-run document framework saved to a dedicated worktree for clear execution handoff.

When do I need to generate a standardized plan document for engineering tasks?

You need to generate a standardized plan document when starting a new feature with a vague spec to reduce ambiguity, enforce a repeatable process, and provide a clear execution handoff.