staff-writing-plans

Transform specs and requirements into executable implementation plans with file-by-file tasks.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/HexSleeves/skills --skill staff-writing-plans
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: staff-writing-plans
Source: https://github.com/HexSleeves/skills/tree/main/skills/staff-writing-plans
Command: npx skills add https://github.com/HexSleeves/skills --skill staff-writing-plans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this Skill when you have a spec or requirements and need a clear, implementation-ready plan before changing code. It turns ambiguous work into a structured path that another engineer or agent can follow with minimal context.

Core Features & Use Cases

  • File-by-file planning: Identifies exactly which files to create or modify and what each one is responsible for.
  • Bite-sized execution steps: Breaks work into small, TDD-friendly actions with precise commands, expected outcomes, and commit points.
  • Quality safeguards: Includes self-review checks for missing requirements, placeholder language, and type or naming consistency before handoff.
  • Use cases: Ideal for multi-step feature work, refactors, bug fixes, or any task that should be delegated with a reliable implementation roadmap.

Quick Start

Use the writing-plans skill to turn this specification into a detailed implementation plan with files, tests, and step-by-step tasks.

Frequently Asked Questions about staff-writing-plans

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

FAQPage Schema
How do I turn software specifications into an implementation plan?▼

To turn specifications into an implementation plan, you decompose requirements into file-by-file task mapping, TDD-oriented steps, exact test commands, and commit guidance for agentic execution.

What is the best way to break down a feature spec for delegated coding tasks?▼

The best way to break down a feature spec for delegated tasks is creating bite-sized execution steps with precise commands, expected outcomes, and self-review checks for missing requirements or type consistency.

How do I plan a multi-step code refactor using TDD?▼

Plan a multi-step code refactor using TDD by mapping file modifications, defining exact test commands, and establishing commit points to verify expected outcomes before handoff.

Can I use this approach for complex bug fixes requiring worktree isolation?▼

Yes, you can use this approach for complex bug fixes requiring worktree isolation by generating a structured, task-decomposed roadmap that another engineer or agent can follow with minimal context.

Does the generated implementation plan include checks for placeholder language?▼

Yes, the implementation plan includes quality safeguards with self-review checks for missing requirements, placeholder language, and type or naming consistency before handoff.