omp-flow: Skill for Claude Code

OMP-Flow Design

Preconditions

• The assignment identifies the Bundle root, role, objective, selected synthesis entry Concept, allowed output paths, actor ID, and receipt.
• Source provenance needed for the design is readable through ordinary links.

Code layouts (on demand)

Read only for the matching code-design question; resolve the installed path from the project root, not from the Skill directory:

• Caller, interface, data-shape, and ownership design: .omp-flow/workflow/code/architect.md.

Procedure

Main/coordinator alone dispatches, correlates receipts, records human calibration, and chooses transitions. A dispatched Architect performs only the bounded Design responsibility and assigned PRD/Design/decision/interface outputs; it does not dispatch, govern, calibrate, transition, or reinterpret coordinator clauses. It explains each proposed component's concrete causal purpose in plain language, without relying on its own terminology, and solves the evidenced principal contradiction rather than a secondary or invented mechanism.

1. In Main/coordinator context only, dispatch the native Architect with Bundle root, selected synthesis entry, bounded objective, relevant linked Concepts, explicit output ownership, actor ID, and receipt. Create the operation first and forward its complete returned assignment unchanged to the native agent matching the descriptor role. Preserve the strict v1 ompFlowDispatch descriptor as the first non-blank line.
2. Rewrite prd.md into observable requirements, non-goals, constraints, acceptance criteria, and unresolved product decisions. Remove temporary brainstorm duplication.
3. Write design.md with components, interfaces, data flow, state ownership, error behavior, migration/compatibility, verification strategy, and rejected alternatives. Specify decisions and exact signatures rather than full implementation transcripts; include a code body only for a non-obvious algorithm that signatures and test assertions do not determine.
4. Add linked decision, interface, brief, or finding Concepts only when they improve navigation or reuse. Their directories and filenames are descriptive, not tiers or identifiers.
5. Express binding constraints precisely and retain links to the synthesis or source Concepts.
6. Review PRD, Design, and linked Concepts as the builder who will implement them without guessing: check for contradictions, placeholders, unowned decisions, implied input classes or failure modes not yet pinned to verification, requirements with no verification path, and code-transcript bloat.