decided-review

AsDecided corpus review

decided review <dir> validates every artifact, checks every relationship, and reports findings grouped by priority, worst first. This skill is the procedure for working that report down: blocking findings first, then advisory ones, re-validating after each fix.

Hard constraints

• Write artifact files only inside the host project's decisions directory (decisions/ by default; if the project keeps artifacts elsewhere, confirm the path before writing). Never create or edit RAC artifacts outside that directory, and never modify files elsewhere in the project on this skill's behalf.
• Never hand-write or alter an artifact id or its frontmatter identity block. Do not edit .decisions/config.yaml.
• Do not invent sections or frontmatter fields. Use decided schema <type> to see what a type expects.
• The work is done only when decided validate <dir> and decided relationships <dir> --validate both exit 0.

Run the review

decided review <dir>            # findings grouped by priority, worst first
decided review <dir> --json     # stable contract for scripted triage

Exit 1 means blocking findings exist; exit 0 with findings means only advisory items remain. Findings are grouped by priority:

1. Invalid artifacts — validation errors (blocking)
2. Broken relationships — unresolvable references (blocking)
3. Unrecognized artifacts — no schema matched (advisory)
4. Missing recommended information (advisory)

Work strictly in priority order. Each finding carries a suggested action; start from it.

Mechanical findings — missing sections

Missing recommended sections are mechanical: the fix is adding the section with real content.

decided improve <file>             # missing sections, with guidance prompts
decided improve <file> --template  # Markdown stubs for the missing sections

Paste the stub, then replace its placeholder text with real content. Do not add a section purely to silence a finding — when no real content exists, an advisory finding may stand.