ido4specs Pipeline

Three phases turn a written spec into a structured technical spec your team or downstream tools can ingest. You review at every phase boundary — nothing auto-progresses.

ido4 suite
ido4shape
WHY and WHAT
Claude Cowork
→
ido4specs
WHAT and HOW
Claude Code · this plugin
→
ido4dev
Execution
Claude Code + GitHub issues
Pipeline
Input
Strategic spec
.md file you bring
→
Phase 1
~15–30 min
Read & explore
/create-spec
Reads your spec, then explores your codebase (or integration targets if greenfield) to ground each capability in real file paths and patterns.
→Technical canvas
→
Phase 2
~10–20 min
Decompose into tasks
/synthesize-spec
Turns each capability into right-sized tasks with effort, risk, AI suitability, dependencies, and verifiable success conditions.
→Technical spec (.md)
→
Phase 3
~2–5 min each
Review & validate
Two skills cross-check the spec from different angles.
1. Deterministic pass
/validate-spec
Parser checks structure, metadata, and content rules.
2. Qualitative pass
/review-spec
LLM review of quality, code-grounding, and consistency.
If findings: /refine-spec applies edits + re-validates.
You review the canvas
You review the tech spec
You decide it's ingestion-ready
Artifact lifecycle
Input
Strategic spec
From ido4shape or hand-authored. The WHAT, not the HOW.
→
After Phase 1
Technical canvas
Strategic context preserved + per-capability codebase analysis: relevant modules, patterns, dependencies, complexity.
→
After Phase 2
Technical spec
Capabilities decomposed into tasks. Per task: effort, risk, type, AI suitability, depends_on, success conditions.
→
After Phase 3
Ingestion-ready
Plain markdown. Pipe to ido4dev for GitHub issues, your own ticket system, or any downstream tool.