Internal shared skill. Referencing workflows keep stage numbers, artifact destinations, and intentional divergences; this skill is the single source of truth for review and verification-report orchestration.
Prerequisite check: verify each declared dependency is available when this skill is loaded. If one is missing, stop and print
npx skills add FuDesign2008/open-skills -g --skill '*' --yes; do not silently reduce the review.
Placeholder contracts
| Placeholder | Meaning | Referencing workflow supplies |
|---|---|---|
{next-stage} |
The stage entered after a passed review | Number and name |
{artifact-sink} |
Where review records or the design summary are persisted | Host-specific path or artifact |
{extra-dimensions} |
Additional host-only dimensions | Required checks and their sink |
{batch-overcap-behavior} |
Action after the automatic three-round limit in batch contexts | Host-specific behavior, or N/A |
Never hardcode a host workflow's stage numbers, OpenSpec paths, Jira state transitions, or batch policy.
Review contract
- Always load and run the complete
solution-reviewframework: all core dimensions and strategic dimensions at the depth determined by reversibility. - When the solution affects code, also load and run
code-design-reviewLayer A/B/C according to its applicability rules. - Apply
{extra-dimensions}after the shared reviews. These checks supplement, never replace,solution-review. - Aggregate the review skills' blocking criteria into a binary result:
- Pass: no blocking issues remain.
- Fail: at least one blocking issue remains.
- Write the review record and passed design summary to
{artifact-sink}.
Review loop and gates
- In automatic mode, on failure optimize the solution, record the optimization, and rerun the full review. The initial review plus at most two optimized re-reviews is a three-round limit.
- At the limit, pause for the user unless
{batch-overcap-behavior}specifies the host's batch handling. - In manual mode, present the review report and wait for the user to approve, revise, or reselect the solution. Do not advance without an explicit user decision.
- A pass enters
{next-stage}. A fail remains in solution optimization or returns to solution selection as directed by the user.
Design summary
After a passed review, emit a structured design summary with goals, non-goals, decisions, risks and mitigations, and open questions. It is part of the review output, not a separate mandatory file, unless {artifact-sink} requires persistence.
Verification-report honesty
Every verification result must disclose its execution state:
- Executed: include the command or action and a concise output/result summary.
- Pending: name the precise manual action still required.
Do not report designed scenarios or inferred correctness as completed verification. Browser or other unavailable manual interactions remain pending with actionable instructions.
Integration guide
Referencing workflows must:
- Declare
pdca-review-orchestrationin frontmatter dependencies and perform their normal dependency gate. - At the review stage, load this skill and map all placeholders using numbers and names where applicable.
- Keep only host orchestration: stage exit wording,
{extra-dimensions},{artifact-sink}, and{batch-overcap-behavior}. - Point their verification stage to this skill's honesty rule in one sentence.
Do not duplicate binary tables, blocking lists, three-round loop prose, design-summary templates, or verification-honesty blocks in hosts.