writing-plans

Generates step-by-step implementation plans from feature specifications.

2|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/passionseed/ps_app --skill writing-plans-passionseed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/passionseed/ps_app/tree/main/.agent/skills/writing-plans
Command: npx skills add https://github.com/passionseed/ps_app --skill writing-plans-passionseed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. Frequent commits.

Core Features & Use Cases

  • End-to-end planning for features from spec to deployment.
  • Include precise file paths, tests, docs, and commit messages.
  • Use cases: rapidly plan tasks for unfamiliar codebases.

Quick Start

Generate a complete implementation plan by describing the feature and target environment, then outline concrete tasks with exact file paths, tests, docs, and commits.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create a detailed implementation plan for an unfamiliar codebase?

Generate a step-by-step implementation plan from a feature specification, breaking down tasks into bite-sized steps with exact file paths, tests, and documentation for engineers lacking codebase context.

What is task-breakdown planning for test-driven feature development?

Task-breakdown planning structures a feature specification into sequential implementation tasks. It includes exact file touchpoints, test-driven development checks, documentation updates, and structured commits.

How do I plan codebase changes with exact file paths and structured commits?

Plan codebase changes by generating a step-by-step implementation plan specifying exact file paths, required tests, documentation, and frequent structured commits for each bite-sized task.

Can I use generated implementation plans for an execute-plan workflow?

Yes, generated implementation plans use a format compatible with the execute-plan workflow. They satisfy frontmatter-based metadata requirements and explicit task structure for seamless execution.

Does implementation planning work for engineers with zero codebase context?

Yes, implementation planning is designed for engineers with zero codebase context. It documents everything needed, including which files to touch, code, testing, and docs to check for each task.