speckit-order

Document the Speckit workflow execution order and dependencies.

1|Updated Nov 28, 2025

Search Tags:#workflow #specification #dependencies #orchestration #speckit #ai-coding

Ready to run

npx skills add https://github.com/FnSK4R17s/chakravarti-cli --skill speckit-order

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-order
Source: https://github.com/FnSK4R17s/chakravarti-cli/tree/main/.agent/skills/speckit-order
Command: npx skills add https://github.com/FnSK4R17s/chakravarti-cli --skill speckit-order

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-order provides a definitive reference for the execution order and dependencies of speckit workflows, ensuring teams align on the sequence from constitution to implement.

Core Features & Use Cases

Reference guide for the Speckit execution order from constitution to implement.
Dependency mapping showing which workflows rely on outputs from previous steps.
Use Case: When starting a new Speckit project, consult this reference to plan the alignment of /speckit.* stages.

Quick Start

Review this reference to understand the required Speckit execution sequence and dependencies, and apply it to align your speckit workflows.

Frequently Asked Questions about speckit-order

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

FAQPage Schema

What is the required execution order for a Speckit workflow pipeline?▼

The required Speckit workflow execution order progresses sequentially from constitution to specify, plan, tasks, analyze, and finally implement. This reference clarifies the exact sequence and dependencies to coordinate cross-artifact work effectively.

How do Speckit workflow dependencies map across different stages?▼

Speckit dependencies map by linking each workflow stage—such as plan or tasks—to the specific outputs of preceding steps. This dependency mapping ensures that downstream stages rely on completed upstream artifacts before execution begins.

When do I need to define workflow orchestration dependencies for an AI coding project?▼

You need to define workflow orchestration dependencies when starting a new Speckit project to align cross-artifact stages. Consult this reference to plan the alignment of /speckit.* stages and ensure correct tool usage throughout the pipeline.

Can I use Speckit to coordinate cross-artifact work without specifying execution order?▼

No, using Speckit without specifying execution order risks misalignment across cross-artifact work. Defining the required sequence and dependencies between stages like constitution and implement is necessary to guide tool usage and ensure pipeline integrity.

What are the limitations of using a basic reference guide for workflow orchestration dependencies?▼

The limitation of this basic reference guide is that it only documents the workflow execution sequence and dependencies rather than actively enforcing them. Teams must manually apply the mapped Speckit stages to coordinate their cross-artifact work.