speckit-workflow

Apply a constitution-driven workflow from specification to implementation phases.

432|40|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/tzachbon/smart-ralph --skill speckit-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-workflow
Source: https://github.com/tzachbon/smart-ralph/tree/main/plugins/ralph-speckit/skills/speckit-workflow
Command: npx skills add https://github.com/tzachbon/smart-ralph --skill speckit-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solves governance gaps in feature development by applying a constitution-driven workflow.

Core Features & Use Cases

  • Defines a repeatable workflow for moving from constitution to plan to tasks to implement.
  • Guides cross-phase alignment with quality checkpoints and artifact templates.
  • Use Case: A product team introduces a new feature by creating spec, plan, tasks, and implementation steps following the speckit workflow.

Quick Start

Run speckit-workflow to bootstrap a feature lifecycle: specify, plan, tasks, and implement in sequence.

Frequently Asked Questions about speckit-workflow

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

FAQPage Schema
How do I enforce a governance workflow during feature development?

You enforce a governance workflow by applying a constitution-driven process that guides teams through separated phases: specify, plan, tasks, and implement. This enforces artifact templates and cross-artifact analysis to ensure consistent, auditable delivery.

What is constitution-driven feature development and when is it needed?

Constitution-driven feature development is a phased delivery process that establishes formal governance rules before specification. It is needed when projects require strict quality checkpoints, phase separation, and repeatable workflows to close governance gaps.

How do I move from specification to implementation in a structured workflow?

You move from specification to implementation by following a sequence of phases: specify, plan, tasks, and implement. The workflow enforces artifact templates and cross-phase alignment to guide teams through structured delivery.

Does constitution-driven workflow require quality checkpoints between phases?

Yes, constitution-driven workflow requires quality checkpoints between phases. It guides cross-phase alignment by enforcing artifact templates and separation between the specify, plan, tasks, and implement stages to maintain auditability.

What's the best way to ensure auditable delivery for new product features?

The best way to ensure auditable delivery is by using a repeatable workflow that applies formal governance from the start. This involves creating spec, plan, tasks, and implementation steps while enforcing artifact templates and cross-artifact analysis.