Generate step-by-step implementation plans from a feature spec.
npx skills add https://github.com/lucasreydman/lloyd --skill writing-plans-lucasreydman
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/lucasreydman/lloyd/tree/main/skills/superpowers/skills/writing-plans Command: npx skills add https://github.com/lucasreydman/lloyd --skill writing-plans-lucasreydman
Generate comprehensive implementation plans from a spec to guide engineers who have zero context about the codebase. The plan details which files to touch for each task, the necessary code, tests, and documentation to check, and structures the work into bite-sized steps that support TDD and frequent commits.
Use this skill to generate a detailed implementation plan from a feature spec and save it to docs/plans/YYYY-MM-DD-<feature-name>.md.
High-intent search queries and answers about installing and using this skill.
To convert a feature spec into an implementation plan for test-driven development, this skill structures your work into bite-sized tasks. It enumerates touched files, code changes, required tests, and documentation to support frequent commits.
Generating step-by-step development tasks for engineers with zero codebase context requires detailing required files, components, tests, and verification steps. This skill automates that breakdown from your spec to guide developers through each change.
The best way to document implementation plans for consistent project workflows is saving them with a standardized header. This skill automatically writes generated plans to docs/plans/YYYY-MM-DD-<feature-name>.md to ensure uniform documentation.
Yes, this planning skill works directly with test-driven development workflows. It explicitly structures the generated implementation plan into bite-sized tasks that support TDD methodologies and frequent code commits.
You can enumerate touched files and required tests automatically from a feature spec by processing it through this skill. It analyzes the input to detail necessary code changes, documentation, and verification steps for each task.
A limitation of generating development plans from a spec is that the output quality depends entirely on the provided spec's detail. The skill structures the plan and enumerates files, but cannot infer unstated requirements or verify codebase compatibility.
htlin222Generate structured implementation workflows from PRDs and feature requirements.
AlphaLab-USTCCreate implementation plans with exact file paths and verification commands.
RheasilviaGenerate test-driven implementation plans with file paths for coding tasks.
polikeijiCreate implementation plan documents for architecture, data models, APIs, and tasks.
