flow-spec

Generates structured NLSpec specifications from multi-provider AI research and consensus.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/GongYuanCaiJi/dsh-claude-octopus --skill flow-spec-gongyuancaiji
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flow-spec
Source: https://github.com/GongYuanCaiJi/dsh-claude-octopus/tree/main/.claude/skills/flow-spec
Command: npx skills add https://github.com/GongYuanCaiJi/dsh-claude-octopus --skill flow-spec-gongyuancaiji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing software specifications from a single perspective often misses edge cases, unstated assumptions, and constraint interactions, leading to ambiguous implementation targets and costly rework. This Skill produces a structured NLSpec specification grounded in multi-AI research, adversarial review, and completeness validation. ## Core Features & Use Cases - Multi-AI Research Probe: Dispatches specification research through orchestrate.sh to external providers (Codex, Antigravity) and synthesizes the consensus findings. - Structured NLSpec Template: Generates a complete spec with Purpose, Actors, Behaviors (triggers, preconditions, steps, postconditions, edge cases), Constraints, Dependencies, and an Acceptance Definition with a satisfaction target. - Adversarial Completeness Challenge: Routes the draft spec to a different provider (or a Sonnet agent) to find missing requirements, overlooked constraints, and untestable postconditions before finalizing. - Use Case: Run /octo:spec user authentication system to answer clarifying questions about actors and constraints, then receive a validated spec.md with 3-7 testable behaviors and a satisfaction target calibrated to complexity. ## Quick Start Ask the assistant to create an NLSpec specification for your feature, for example: generate a structured specification for a user authentication system covering actors, behaviors, and constraints.

Frequently Asked Questions about flow-spec

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

FAQPage Schema
How do I generate a software specification from multi-AI research?▼

Invoke the flow-spec skill with a project description, answer the clarifying questions about actors, constraints, and complexity, and it runs orchestrate.sh to gather multi-provider research before synthesizing a structured NLSpec document.

What sections does an NLSpec specification contain?▼

An NLSpec contains six sections: Purpose, Actors, Behaviors (with triggers, preconditions, steps, postconditions, and edge cases), Constraints, Dependencies, and an Acceptance Definition with a satisfaction target between 0.0 and 1.0.

Can I use flow-spec without external AI providers installed?▼

No. The skill checks provider availability and stops if no external providers like Codex or Antigravity CLI are available, suggesting you run the setup command first. Claude handles synthesis but the research probe requires at least one external provider.

What happens if the orchestrate.sh probe fails during spec generation?▼

The skill validates that a probe synthesis file exists before proceeding. If validation fails, it reports the error, shows logs from the claude-octopus logs directory, and stops rather than substituting direct single-model analysis.

How does the adversarial review improve specification quality?▼

After drafting, the spec is sent to a different provider (or a Sonnet agent) instructed to find missing requirements, overlooked constraints, and untestable postconditions. Valid challenges are incorporated and the review outcome is recorded in the spec's Meta section.

When should I skip the adversarial completeness challenge?▼

Skip it with the --fast flag or when speed matters more than thoroughness. The challenge step is marked recommended, while the probe execution and completeness validation gates remain mandatory.