Menu
Review what was built against the plan and design. Flags gaps, regressions, and deviations. Writes review.md.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Convene the Council of High Intelligence — multi-persona deliberation with historical thinkers for deeper analysis of complex problems.
Design Audit — multi-angle review of a detailed design against the actual codebase before implementation.
Mark a TDD design as complete — stamp completion, archive handoff.md, archive to three-pillars-docs/completed-tp-designs/, and optionally commit + open a PR merging the design branch back to the base branch.
Scaffold architecture.md, product_roadmap.md, and known_issues.md in three-pillars-docs/ from codebase analysis. Creates the three project docs that the TDD pipeline reads for context. Assumes three-pillars-docs/vision.md already exists — if missing, recommends /tp-setup first.
Read project docs and propose what to do next. Surfaces highest-impact work from roadmap, known issues, and in-flight designs.
Final audit of a completed plan — verify the full implementation against both design.md and detailed-design.md.
| name | tp-phase-review |
| description | Review what was built against the plan and design. Flags gaps, regressions, and deviations. Writes review.md. |
| argument-hint | {design-name} [phase-number] [--force-takeover] |
Review the implementation against the design and plan artifacts.
Argument: {design-name} (required), optionally followed by a phase number to review only that phase.
three-pillars-docs/tp-designs/{design-name}/plan.md must exist with at least some tasks marked as Done.Run first-run preflight per skills/_shared/first-run.md.
Run collaboration preflight per skills/_shared/collaboration.md with phase: "review". This verifies the branch and refreshes the lock so review.md is written by the rightful owner. Honor --force-takeover if passed.
Read all design artifacts: design.md, detailed-design.md, plan.md from the design directory.
For each completed task in plan.md:
Run the full test suite for all affected files. Discover the test command from the project config (CLAUDE.md, Makefile, package.json, pyproject.toml, etc.):
{project-test-command} 2>&1 | tee "$(mktemp /tmp/test_output.XXXXXX.log)"
Check for gaps:
Write three-pillars-docs/tp-designs/{design-name}/review.md:
# <Design Name> — Review
## Summary
<2-3 sentences: overall status, confidence level>
## Completed
| Task | Tests | Implementation | Notes |
|------|-------|----------------|-------|
| 1.1 | ✓ | ✓ | |
| 1.2 | ✓ | ~ | Deviates from interface spec: ... |
## Gaps
- <behavior or edge case not covered>
## Deviations
- <intentional or accidental departures from the design>
## Test Results
<paste test output summary>
## Recommendations
- <what to do about gaps/deviations — add tasks, update design, or accept>
skills/_shared/commit-after-work.md. Artifact paths to stage:
three-pillars-docs/tp-designs/{design-name}/review.mdthree-pillars-docs/tp-designs/{design-name}/lock.json (if refreshed)
Commit message: Review: {design-name} phase-{n} (use the phase number if one was given; otherwise omit phase-{n}).{design-name} per skills/_shared/validate-name.md.skills/_shared/collaboration.md — review artifacts written by a non-owner cause confusion. The preflight step can refuse to proceed unless --force-takeover is passed.