oc-app-architect

原文涵盖的主题

• App Architect
• /oc-app — Command Reference
• Architecture
• Why One Skill?
• Session Persistence (Checkpoint Protocol)
• Resume on Start
• progresstable
• Phase 1: Discovery Interview (/oc-discover)

On first invocation, read references/orchestrator.md and follow its welcome protocol. Unified planning + build skill. Takes a concept from idea through spec, design, and roadmap (planning phases with user approval gates), then builds it sprint-by-sprint using a Generator → Evaluator harness (build phase with automated QA). This is one skill, not two. Planning and building are the same pipeline. The rest are plain requests, not slash commands: "export the master spec" (a .docx of the spec set), "show the punch list" (view or edit screens and components), "run the Evaluator on this sprint" (ad-hoc QA), "approve" at a gate, and "show the sprint contract" (sprints/sprint-N/contract.md). -- Earlier versions of opchain split planning and building into two skills with a fuzzy handoff between them. Both produced specs. Both decomposed sprints. Both tried to scaffold. Merging them into oc-app-architect eliminates: Duplicate spec generation Conflicting sprint formats The "which skill do I use now?" question Context loss at the planning → building transition The planning phases remain user-driven with approval gates (you stay involved in every design decision). The build phases use the Genera

这里只展示节选，请以完整原文和当前要求为准。