Plan multi-step software tasks from a spec before coding.
npx skills add https://github.com/frap129/dotfiles --skill writing-plans-frap129
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/frap129/dotfiles/tree/main/.config/opencode/skills/writing-plans Command: npx skills add https://github.com/frap129/dotfiles --skill writing-plans-frap129
Use when you have a spec or requirements for a multi-step task, before touching code. This skill helps engineers map out the entire plan, identify files to touch, tests to write, docs to check, and maintain a record of tasks and commits.
Plan the full implementation by outlining tasks, touched files, tests, docs, and commits.
High-intent search queries and answers about installing and using this skill.
To plan multi-step software tasks, outline the full implementation by detailing specific file touches, tests to write, documentation to check, and incremental commit history. This approach enforces a repeatable plan format to guide complex feature implementation.
Task decomposition in software engineering is breaking down complex features into actionable steps. It involves mapping out file modifications, testing requirements, documentation updates, and commit strategies using DRY, YAGNI, and TDD mindsets to keep plans concise.
You can create an implementation plan with limited codebase context by following a structured format that identifies files to touch, tests to write, and docs to check. This planning skill works effectively even when engineers have zero or limited prior knowledge of the codebase.
You need to map out files and tests for a feature spec before touching code. This comprehensive task decomposition is required when you have requirements for multi-step software work and need clear guidance on commit strategy and incremental implementation.
Yes, test-driven development planning helps with incremental commits by enforcing a repeatable plan format. It outlines tasks, touched files, tests, and documentation alongside a commit history strategy to guide incremental implementation across complex features.
The best way to structure a plan for complex software features is using a repeatable format with dedicated sections for tasks, files, tests, docs, and commit history. This ensures comprehensive task decomposition and keeps implementation concise and actionable.
poko8nadaGuide teams to gather requirements, define MVP scope, and break down tasks.
jaydubya818Execute work plan documents end-to-end with task generation and quality gates.
rlagycksEstablish test-driven development workflows for Laravel projects using PHPUnit and Pest.
ArchitectVS7Orchestrate GitHub project management workflows with AI swarms for issue tracking and sprint planning.
