sdd-forge.flow-plan

Formalize end-to-end software planning workflows from requirements through test planning.

2|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/SpreadWorks/sdd-forge --skill sdd-forge-flow-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-forge.flow-plan
Source: https://github.com/SpreadWorks/sdd-forge/tree/main/src/templates/skills/sdd-forge.flow-plan
Command: npx skills add https://github.com/SpreadWorks/sdd-forge --skill sdd-forge-flow-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The SDD Flow Plan provides a structured, repeatable approach to planning software changes from initial requirements through test planning, reducing ambiguity and accelerating delivery.

Core Features & Use Cases

  • End-to-end planning for feature work, bug fixes, and design changes, covering requirements gathering, spec creation, gate checks, and test planning.
  • Automated progress tracking and context recording to ensure auditable decisions and traceability across the planning lifecycle.
  • Guardrail-driven decision points and templates to align teams on scope, constraints, and acceptance criteria.

Quick Start

Describe a feature or fix request to generate the full spec and test plan.

Frequently Asked Questions about sdd-forge.flow-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is end-to-end software feature planning?

End-to-end software feature planning formalizes workflows from requirements gathering through test planning. It covers spec creation, gate checks, and approval phases to ensure comprehensive, auditable plans and reproducible outcomes.

How do I create a test plan from a feature request?

Describe a feature or fix request to generate the full spec and test plan. The workflow guides spec creation, applies gate checks, and tracks progress to ensure traceability across the planning lifecycle.

Can I use this workflow for bug fixes and design changes?

Yes, you can apply this workflow to feature requests, bug fixes, and design changes. It enforces guardrails, records context, and tracks progress to ensure comprehensive, auditable plans for any software modification.

What's the best way to enforce guardrails during spec creation?

The best way to enforce guardrails is using guardrail-driven decision points and templates. These align teams on scope, constraints, and acceptance criteria while recording context for auditable decisions.

How does automated progress tracking work for software planning?

Automated progress tracking records context and monitors workflow stages to ensure auditable decisions and traceability. It enforces gate checks across the planning lifecycle to yield reproducible outcomes.