Create detailed implementation plans with file impact mapping and task decomposition.
npx skills add https://github.com/LuizEduPP/skills --skill writing-plans-luizedupp
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/LuizEduPP/skills/tree/main/writing-plans Command: npx skills add https://github.com/LuizEduPP/skills --skill writing-plans-luizedupp
The writing-plans skill keeps engineers from diving straight into implementation by forcing them to document the required files, tests, and procedures for every multi-step spec as a shared, actionable plan before writing any code.
Use the writing-plans skill to draft a detailed implementation plan covering files, tests, tasks, and commits before coding begins.
High-intent search queries and answers about installing and using this skill.
To create an implementation plan, you map file impacts, decompose tasks into step-by-step instructions with code samples, define testing strategies, and establish a commit workflow before coding begins.
Task decomposition and file impact mapping involve identifying all files to create or modify for a spec, breaking down multi-step engineering work into bite-sized tasks, and flagging specs that need splitting into independent subsystems.
Structure an engineering plan by starting with a required header, writing per-task steps with explicit file edits and command expectations, saving it under a docs path, and running a three-part self-review checklist to verify completeness.
You should split a large spec into independent subsystem implementation plans during file impact mapping when scope checks reveal the engineering task is too broad to be handled by a single multi-step plan.
Writing an implementation plan includes testing strategy and commit workflow guidance by emphasizing Test-Driven Development (TDD), specifying frequent commits, and providing explicit tool context expectations for each task.
The best way to document required files and procedures is to generate a structured, actionable plan that details file edits, tests, commands, and commit instructions, preventing engineers from diving straight into coding.
family3253Generate step-by-step implementation plans from project specs.
alffeiGenerate implementation plans for multi-step software tasks with date-based filenames.
CharlesWiltgenExtract WWDC transcripts, code samples, and Apple documentation with timestamps.
zMynxxDispatch development tasks to subagents with review checkpoints.
