phase-review_skill

This skill reviews phase implementation plans for flaws without altering the plan, offering suggestions for improvements.
  • Shell

30

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill mcouthon/agents --skill phase-review

  • SKILL.md864 B

Overview

This skill reviews implementation plans for a single phase inside a larger task and flags flaws, gaps, and risky assumptions before execution. It returns actionable suggestions and clear findings for the orchestrating agent to present to the user. It does not edit plan files but instructs the orchestrator on status updates and notes to record.

How this skill works

Given a phase plan from the .tasks/ directory, the skill reads the plan context and checks for missing steps, unclear acceptance criteria, hidden dependencies, and unrealistic time estimates. It compares the phase tasks to the overall task context to ensure alignment and detects potential regressions or security and deployment risks. The skill outputs a concise review, prioritized recommendations, and a single status change instruction for the task.md file.

When to use it

  • Before committing a phase to execution
  • When a phase plan is newly authored or modified
  • When verifying correctness against overall project context
  • When release windows, security, or infra constraints matter
  • When acceptance criteria or testing steps seem vague

Best practices

  • Preserve the original plan file; provide suggestions separately
  • Confirm the overall task context before recommending removals
  • Prioritize safety, testability, and rollback options in recommendations
  • Call out missing acceptance criteria and measurable success signals
  • Recommend small, testable increments rather than large risky changes

Example use cases

  • Review a development phase for missing unit/integration tests and rollout steps
  • Validate a deployment phase for missing rollback or monitoring hooks
  • Check a migration phase for data integrity and backward-compatibility assumptions
  • Verify time estimates and concurrent dependency coordination before scheduling

FAQ

No. I only produce review findings. I instruct the orchestrator to update the phase status in task.md to Reviewed and to add notes if relevant.

What format do you return suggestions in?

I return a concise, prioritized list of findings and suggested changes. Each item explains the issue, its impact, and a recommended fix or mitigation step.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational