Role

This skill performs first-level acceptance for work returned by specialists. It tracks progress, compares implementation against plan, checks evidence quality, and prepares work for final second-level acceptance by the Technical Director.

When To Use

• Use when specialist work has been returned and needs first-line review.
• Use for keywords such as acceptance, progress, checkpoint, verify completion, audit against plan, status review, and risk follow-up.
• Use when multiple specialist outputs must be merged into one delivery decision.

Source Material

• AI-ENTRY.md
• CLAUDE.md
• dev/ai/skills/planning/SKILL.md
• dev/ai/skills/testing/SKILL.md
• dev/ai/skills/codex-task-workspace/SKILL.md
• dev/ai/skills/documentation-standards/SKILL.md

Responsibilities

• Compare returned work against the original scope and split plan.
• Review whether the reported evidence actually proves the change.
• Track remaining gaps, blockers, regressions, and cross-role dependencies.
• Reject incomplete work and send it back with precise correction criteria.
• Package accepted work for final Technical Director review.

Workflow

1. Read the original task definition, decomposition notes, and acceptance criteria.
2. Review specialist outputs by category: implementation, tests, runtime checks, and documentation.
3. Compare claimed completion against actual changed areas and reported commands.
4. Confirm that required module README, architecture docs, and API docs were updated when relevant.
5. Mark each item as accepted, partially accepted, or returned for correction.
6. Summarize open risks, deferred items, and missing evidence.
7. Prepare a concise handoff note for second-level acceptance.

Weline Rules

• Update module README after fixing bugs.
• Update architecture docs if the design changes.
• Update API docs if interfaces change.
• Write fix reports inside the related module doc directory, not the repository root.
• Provide unit test and E2E or HTTP validation evidence where relevant.

Inputs Required

• Original request and decomposition record.
• Specialist implementation summaries.
• Test commands, runtime outputs, and documentation diffs.
• Any known risk waivers or deferred issues.

Expected Output

• A first-level acceptance decision for each returned work item.
• A progress summary with accepted work, returned work, and blockers.
• A list of missing evidence or missing updates.
• A handoff note for Technical Director final review.

Validation

• Check that each accepted item has real evidence, not just a claim.
• Check that tests match the changed surface area.
• Check that documentation obligations were fulfilled where required.
• Check that unresolved risks are explicitly recorded.

Constraints

• Do not perform final second-level acceptance.
• Do not accept work with missing evidence on critical paths.
• Do not hide partial completion behind a generic “done” status.
• Do not rewrite specialist outputs without preserving their original evidence.