Plan Mini-SDD workflows and generate `.spec/<feature-slug>/plan.md` for smaller software changes.
npx skills add https://github.com/nushey/sdd-flow --skill mini-sdd-planner
Please help me install this Agent Skill. Skill: mini-sdd-planner Source: https://github.com/nushey/sdd-flow/tree/main/skills/mini-sdd-planner Command: npx skills add https://github.com/nushey/sdd-flow --skill mini-sdd-planner
It prevents small feature work from becoming ambiguous or inconsistent by forcing a guided intake, grounded research, and a reusable plan contract before any code is written.
.spec/<feature-slug>/plan.md that tells the developer exactly which skills to load and which MCP tools to re-invoke with copy-pastable JSON args.Provide a feature request like “Add OAuth login with Google” and include any relevant existing files so the planner can ground the plan and generate .spec/<feature-slug>/plan.md.
High-intent search queries and answers about installing and using this skill.
Software feature planning requires a guided intake process and grounded research to generate a reusable plan contract. This skill merges scope clarification and technical decomposition into a single orchestration pass to produce a `.spec/<feature-slug>/plan.md` before any code is written.
Spec-driven development for smaller software changes is a workflow that applies structured interrogation and architecture-fit validation to eliminate ambiguity. It forces zero-assumption research and explicit recording of unverified assumptions to prevent drifting or hallucinated implementations.
Preventing implementation drift requires explicitly recording unverified assumptions during the planning phase. This skill uses a structured grilling protocol that validates architecture fit and confirms reference gold standards one question at a time.
Yes, the generated `plan.md` serves as a harness-neutral bootstrap contract that tells the developer exactly which skills to load and which MCP tools to re-invoke with copy-pastable JSON arguments for implementation.
Creating an implementation plan for small refactors or bug fixes requires merging initialization and technical design into a grounded orchestration pass. Provide a feature request and relevant existing files to ground the plan and generate the structured plan document.
Yes, the workflow is harness-neutral and requires zero specific component dependencies. It produces a bootstrap contract containing skill and MCP instructions that can be executed by a developer subagent in any environment.
michael-watsonAnalyze codebase architecture, dependencies, and constraints into a research document.
nusheyOrchestrate a spec-driven workflow from task prompt to approved plan and implementation.
am-willOrchestrate parallel subagents to execute development plan tasks in waves.
ArvorCoAutomate TDD-driven feature implementation with quality gates and PRD alignment.