Convert software design specifications into test-driven implementation plans.
npx skills add https://github.com/SeaBrad72/sparkwright --skill plan-seabrad72
Please help me install this Agent Skill. Skill: plan Source: https://github.com/SeaBrad72/sparkwright/tree/main/skills/plan Command: npx skills add https://github.com/SeaBrad72/sparkwright --skill plan-seabrad72
This skill solves the gap between an approved design and a functional implementation by generating a structured, task-by-task plan that allows any engineer to execute work without prior codebase context.
Ask the agent to walk you through the planning process for your current design spec to generate a build-ready implementation plan.
High-intent search queries and answers about installing and using this skill.
To turn approved software design specs into build-ready implementation plans, you need granular, task-by-task workflows. This process uses INVEST slicing to break designs into independent, testable vertical increments executable by engineers without prior codebase context.
INVEST-based slicing in software development lifecycle planning is a method to break complex designs into small, independent, negotiable, valuable, estimable, small, and testable vertical increments. It ensures each implementation task is granular and verifiable.
To enforce test-driven development planning, mandate that every task is defined by failing tests before implementation. This TDD-first workflow ensures the resulting code is production-grade, verifiable, and executable by engineers lacking prior codebase familiarity.
Control-plane guardrails for CI and governance changes are strict hygiene rules ensuring sensitive tasks are handled safely. They require changes to conformance and governance to be processed via dev-clones and human-verified diffs to maintain architectural integrity.
Software engineering planning can work without prior codebase knowledge when structured correctly. By generating granular, test-driven implementation plans with conformance markers and dual-review gates, any engineer can execute production-grade work safely.
You need dual-review gates in an implementation plan when enforcing rigorous TDD standards and architectural integrity. They act as conformance markers to ensure production-grade output and strict control-plane safety during the software development lifecycle.
zinohomeGuide software ideas through structured brainstorming into approved design specifications.
weipingGenerate step-by-step implementation plans with file, code, and test instructions.
HeadyAIMaps regulations, manages policies, and enforces governance for AI systems.
docs-plusDecompose project plans into structured vertical slice issues with HITL/AFK classification.
