[Feature]: Simplify workflow with optional merged commands for migration from OpenSpec

[liuzhihang]

Problem Statement

As a developer looking to migrate from OpenSpec to Spec Kit, I find the current 6-step workflow (constitution → specify → clarify → plan → tasks → implement) to be too granular and high-friction compared to OpenSpec's streamlined 3-step flow.

For teams already clear on requirements, steps like clarify and plan often feel redundant, adding unnecessary overhead to the development process. This makes migration from lighter-weight specification tools a significant challenge, as the step count alone can discourage adoption.

The core issue is a lack of a "fast path"—a way to merge conceptually related steps into fewer, higher-level commands for teams that don't need the full granularity in every case.

Proposed Solution

Introduce optional "merged" commands or a simplified workflow mode that reduces the core flow from 6 steps to 3, mirroring the OpenSpec experience:

1. /speckit.define — Merges constitution + specify + clarify into a single command.

   • On first run, it prompts for the project constitution and stores it.
   • Subsequently, it takes a feature description, auto-generates the spec, and runs inline clarification questions in one interactive session.

2. /speckit.design — Merges plan + tasks into a single command.

   • Generates both the technical plan and the actionable task breakdown in one pass.

3. /speckit.implement — Remains as-is, executing the generated tasks.

The existing 6 commands would remain untouched, preserving the full granular workflow for teams that rely on it. The merged commands would simply be convenience wrappers that automate the intermediate handoffs.

A configuration flag (e.g., specify workflow --mode simplified) could let teams set this as the default.

Alternatives Considered

1. A --skip flag on individual commands: For example, /speckit.tasks --skip-clarify would generate tasks without requiring a separate clarify step. This is simpler to implement but less cohesive than merged commands.

2. User-defined workflow profiles: Allow teams to configure which steps are mandatory via a .specify/config.yml file. This would be more flexible but also more complex to design and document.

3. Sticking with OpenSpec for simpler projects: The current alternative is simply not migrating, which fragments the tooling ecosystem. This feature would directly address that migration barrier.

Component

CI/CD workflows

AI Agent (if applicable)

All agents

Use Cases

1. Migrating from OpenSpec: A team currently using OpenSpec's 3-step flow wants to adopt Spec Kit's richer feature set without increasing their day-to-day step count.
2. Internal tools & hackathons: Projects where speed matters more than process rigor. A 3-step flow is sufficient for capturing intent and generating code quickly.
3. Iterative bug fixes: When fixing a well-understood bug, running through all 6 steps is overkill. A define → design → implement shortcut would be ideal.
4. Teaching new developers: A simplified path lowers the onboarding curve. New users can start with 3 steps and "unlock" the full workflow as their needs grow.

Acceptance Criteria

• Merged commands /speckit.define and /speckit.design are available and produce the same final artifacts as their multi-step equivalents.
• A --mode simplified (or equivalent) configuration option allows setting this as the default workflow.
• All existing 6-step commands continue to work without any breaking changes.
• Documentation includes a "Simplified Workflow" guide, including a migration guide from OpenSpec.
• The feature works across all officially supported AI agents (Claude Code, Codex, etc.).

Additional Context

This request is inspired by the growing ecosystem of bridges and integrations between Spec Kit and lighter-weight tools. The existence of projects like speckit-superpowers-bridge and the academic "Spec Kit Agents" paper shows a clear demand for workflow flexibility.

OpenSpec's 3-step model (proposal → spec → tasks) has proven highly effective for many teams. While Spec Kit's 6-step model offers superior rigor for complex projects, providing a built-in "fast path" would significantly broaden its appeal and ease the migration path for OpenSpec users like myself.

Related: This feature would complement community extensions that already focus on workflow orchestration.