| name | ecc-role-architect |
| description | Role skill for 'architect'. Use when tasks need architecture design and tradeoff decisions with role-scoped deliverables. |
ecc-role-architect
Design system structure, interfaces, and tradeoffs before implementation.
Role Workflow
- Restate objective through the
architect lens.
- Produce role-specific plan/checklist.
- Execute or guide execution with evidence.
- Emit role-specific verdict and next actions.
Deliverable Format
- Role objective
- Key analysis/findings
- Decisions/tradeoffs
- Action items
- Verification status
Rules
- Stay within role scope; escalate cross-role dependencies.
- Use concise, high-signal outputs.
- Prefer verifiable recommendations.
ECC Parity Notes
- This skill is adapted from ECC intent and translated to OpenClaw-native tool workflows.
- Prefer reproducible, tool-backed execution over harness-specific slash semantics.
- Keep outputs evidence-based and verification-first.
OpenClaw Constraints
- If upstream flow assumes unavailable hooks/tools, use documented fallback scripts in
openclaw-ecc/scripts/.
- Mark non-applicable checks as
SKIP rather than hard-failing when environment support is absent.