Generate structured, test-driven implementation plans with file-level task mapping.
npx skills add https://github.com/arthrod/conejo-skills --skill writing-plans-arthrod
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/arthrod/conejo-skills/tree/main/skills/writing-plans Command: npx skills add https://github.com/arthrod/conejo-skills --skill writing-plans-arthrod
This skill solves the problem of poorly defined or ambiguous development tasks by enforcing a rigorous, test-driven planning process that ensures every feature is broken down into actionable, verifiable steps.
Use the writing-plans skill to generate a detailed implementation plan for the new user authentication module based on the provided requirements document.
High-intent search queries and answers about installing and using this skill.
To create a test-driven development plan, decompose complex features into granular file-level tasks mapped to specific test cases. Enforcing a red-green-refactor workflow ensures every architectural boundary is verifiable and prevents scope creep.
Breaking down software architecture requirements involves mapping out explicit file modifications and creation requirements from project specs. This decomposition establishes clear architectural boundaries and yields actionable, verifiable development steps.
TDD enforcement within an implementation plan mandates a strict red-green-refactor workflow for every decomposed task. This mechanism ensures code quality by requiring specific test cases to pass before progressing to subsequent file-level modifications.
Yes, you can use this to plan refactoring workflows by generating explicit file-level task mapping. It decomposes refactoring efforts into verifiable steps, ensuring DRY principles and preventing architectural drift during code modifications.
You need a structured implementation plan when starting complex feature development that requires clear architectural boundaries. It prevents ambiguous development tasks by ensuring every feature is broken down into actionable, verifiable steps before coding begins.
Your development workflow suffers from scope creep and architectural drift due to poorly defined or ambiguous development tasks. Generating a rigorous, test-driven implementation plan with explicit file paths and commit steps prevents this issue.
Jia-Hong-PengGenerate structured implementation plans from spec.md files using spec-kit workflows.
humansysExecute story plan tasks with TDD cycles and verification gates.
allthingslinuxApply Clean Architecture principles to enforce dependency direction and define layer boundaries in software systems.
bluejayAEnforce the RED-GREEN-REFACTOR cycle for all code development.
