Menu
Architecture review and design skill adapted from ECC architect agent. Use for design validation, trade-off analysis, and system-level decisions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Transform product requirements into a focused UI/UX design brief with screens, flows, visual direction, and optional image-generation concepts. Bridge between product thinking and implementation.
Stage 3 of idea-to-delivery: gated engineering workflow that receives PRD, roadmap, and architecture inputs, decomposes into stories, and executes with TDD, traceability, and review gates.
Planning and decomposition review skill adapted from ECC planner agent. Covers story-set review (Gate 2) and planning consults for upstream skills. PRD-quality review is NOT in scope — that is owned by `woos-product-prd-review-gate`.
Produce a lean story plan (table) for the Gate 3 execution loop — execution order plus diff scope per story. PRD AC is the spec; tests are the verification. No per-story prose documents.
Resolve multi-agent review conflicts with explicit authority matrix, evidence weighting, and escalation criteria.
Independent code/security review gate for Hermes workflow. Uses woos-code-reviewer and woos-security-reviewer where applicable.
| name | woos-architect |
| description | Architecture review and design skill adapted from ECC architect agent. Use for design validation, trade-off analysis, and system-level decisions. |
| origin | ECC-agent-adapter |
| ecc_source_repo | affaan-m/everything-claude-code |
| ecc_source_path | agents/architect.md |
| ecc_source_commit | 0e9f613fd196f6d4157765b17d39c2c42ebbf564 |
woos-feature-design) — produce the engineering design artifact from approved PRD + roadmap + architecturewoos-design-review-gate) — fresh-context independent review of an existing design artifactThis adapter operates in one of three modes; the dispatcher MUST set mode explicitly:
mode: author — produce a design artifact. Output is a draft of docs/engineering/<version>/<feature-id>-design.md plus the structured fields below.mode: review — review an existing design artifact in fresh context. Do NOT modify the artifact; emit findings only.mode: consult — answer a focused architecture question raised by another reviewer. Do NOT produce or modify artifacts.mode: author and mode: review MUST be invoked in separate fresh-context dispatches; the same session cannot fill both roles.
mode (required: author | review | consult)author: approved PRD + roadmap + architecture (+ optional interface summary / UI brief / upstream interfaces)review: design artifact path + linked PRD, roadmap, architecture, and supporting interface/UI context when available + prior review contextconsult: the specific question + the minimum artifacts needed to answer itRuntime budget: must return within max_review_runtime_seconds provided by orchestrator.
woos-product-planner with mode: planning for dependency and sequencing implications, woos-security-reviewer for security-sensitive design risks.all_dimensions_checked: true|falseall_findings_classified: true|falsefeedback_is_single_pass_complete: true|falseprior_review_context_checked: true|falseIf any item is false, continue review only within remaining runtime budget; if budget is exhausted, return BLOCKED.
baseline or deviation.STATUS: PASS | REQUEST_CHANGES | NOT_RUN | BLOCKED
SUMMARY: architecture decision summary
KEY_FINDINGS:
- mismatch/risk/decision items
TRADEOFFS:
- decision, pros, cons, alternatives
REVIEW_DIMENSIONS:
- dimension, status, findings
COMPLETENESS_CHECK:
- all_dimensions_checked
- feedback_is_single_pass_complete
BASELINE_DECISION:
- domain, status(baseline|deviation), adr_path, approval_ref
BLOCKING_FINDINGS:
- empty or concrete blockers
Use REQUEST_CHANGES if design is incomplete, inconsistent, or risky.