oc-reverse-spec

Topics in the source

• Reverse Spec
• Why This Exists
• /oc-reverse-spec — Command Reference
• Command Behavior
• How This Skill Fits the Pipeline
• Read by
• Phase 0: Scope & Orientation
• Determine Input Scope

On first invocation, read references/orchestrator.md and follow its welcome protocol. Read an existing codebase and generate the structured spec documents that oc-app-architect expects as inputs. This is the reverse of the normal pipeline: instead of idea → spec → code, it goes code → spec → pipeline-ready. The build pipeline (oc-app-architect Phase 2 stack decision → Phase 6 build loop) assumes spec documents exist. But most real projects were built before the pipeline existed, or grew organically without formal specs. Reverse-spec bridges that gap — it reads what's actually built and produces the documentation that makes the project legible to the rest of the toolchain. This matters because without specs: oc-app-architect can't generate a roadmap for new features (no baseline to build from) oc-stack-forge can't run a gap analysis (no documented architecture to compare against) oc-app-architect Phase 4 (/oc-roadmap) can't decompose features into sprints, and Phase 6 has no spec.md or sprint-plan.md to build against When the user types /oc-reverse-spec, display this menu: /oc-rev-scan: Run Phase 0 only (orientation). Quick inventory, no deep analysis. Produces the orientation summa

This is an excerpt. Refer to the complete source and its current requirements.