the Compliance & Review Phase of the Analysis-Gated Workflow. Use when iterating analysis based on Software Architect ADR annotations. Ensures full compliance before advancing to implementation planning.
How this skill is triggered — by the user, by Claude, or both
Slash command
/analysis-gated-workflow:03-compliance-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
---
This skill governs the Compliance & Review Phase of the Analysis-Gated Workflow. It is an iterative phase that runs as many times as the Architect requires. Its purpose is to ensure the analysis fully reflects the Architect's intent — incorporating ADR annotations, resolving open questions, and deepening domain-specific understanding until the Architect is satisfied that the analysis is ready to drive an Implementation Plan.
Phase 03 is the gate that protects Phase 04 and Phase 05 from being entered prematurely.
Append the Phase 03 initiating prompt (or iteration prompt) to the ## Prompt Log
section, verbatim.
Scan the entire ANALYSIS document for ADR annotations:
**ADR YYYY-MM-DD:**
| | Info |
| --- | --- |
| **Subject** | [topic] |
| **Status** | DECIDED / PENDING |
| **Context** | [background and considerations] |
| **Decision** | [what was decided] |
| **Consequences** | DO: ... <br/> NOT: ... |
For each ADR found without a corresponding Compliance response:
For each unresolved ADR, identify:
For open questions carried forward from Phase 01 or Phase 02:
Update the affected sections of the ANALYSIS document to reflect full compliance with each ADR. Then, immediately below each ADR, add the compliance response:
**Compliance YYYY-MM-DD:**
| | Info |
| --- | --- |
| **Analysis Updates** | [How the analysis was updated in response] |
| **Sections Affected** | [Which sections were changed] |
The ADR itself is never modified. The compliance response documents what changed and why, so the reasoning chain is fully traceable.
Beyond ADR compliance, Phase 03 is the opportunity to deepen analysis in areas that Phase 02 may not have fully explored:
Only go as deep as the Architect's annotations and prompts indicate is needed. Do not speculate beyond what the evidence and ADRs support.
After completing the iteration, evaluate against the Definition of Ready for Phase 04.
The analysis is ready to proceed to Implementation Planning when ALL of the following criteria are met:
Handling unresolved open questions:
If any open questions remain unresolved when assessing Definition of Ready, the AI must
convert them into placeholder ADRs in the ## Architecture Decision Records section.
This is the only circumstance where the AI may write to the ADR section (normally
ADRs are Architect-only).
Format for placeholder ADRs:
**ADR YYYY-MM-DD:**
| | Info |
| --- | --- |
| **Subject** | [Question text / topic requiring decision] |
| **Status** | PENDING ARCHITECT INPUT |
| **Context** | [Summary of the issue, why it matters, and what the options are] |
| **Decision** | [Most likely options, if known, or "TBD based on Architect input"] |
| **Consequences** | DO: [accepted options] <br/> NOT: [rejected options] |
These placeholder ADRs become blocking — the workflow cannot advance to Phase 04 until the Architect replaces the placeholder content with actual decisions, or deletes the placeholder if it's no longer relevant.
If ANY criterion is not met, document what is missing in ## Open Questions or
convert to placeholder ADRs as appropriate. Do not proceed until the Definition of Ready
is satisfied.
If ALL criteria are met, state clearly:
"Definition of Ready satisfied. All criteria met. Ready for Phase 04 upon Architect approval."
Then wait for the Architect's explicit go signal before advancing.
After each iteration:
Current Phase: PHASE 03
Phase Status: AWAITING ARCHITECT REVIEW
Last Updated: YYYY-MM-DD
Pending Architect Action: Review compliance updates.
Add further ADR annotations if needed,
or signal readiness for Implementation Planning Phase.
"Compliance & Review Phase iteration is complete. All current ADRs have compliance responses. Please review the updates. Add further ADR annotations if corrections are needed, or signal when you are ready to proceed to Implementation Planning Phase."
Phase 03 repeats as follows:
Architect adds ADR annotation
↓
AI reads ADR, updates analysis, adds compliance response
↓
AI assesses readiness for Implementation Planning Phase
↓
If not ready → notify Architect, wait for next annotation or signal
If ready → notify Architect, wait for explicit go signal
↓
Architect signals: "proceed to Implementation Planning Phase"
↓
Governing Workflow advances to Phase 04
There is no limit on the number of iterations. The Architect controls the exit.
Each Compliance & Review Phase iteration is complete when:
AWAITING ARCHITECT REVIEWGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub cucurb-it/analysis-gated-workflow-skills --plugin analysis-gated-workflow