review-assumptions

Audit implementor session reports for risky assumptions and context gaps.

30|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/Codagent-AI/agent-skills --skill review-assumptions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-assumptions
Source: https://github.com/Codagent-AI/agent-skills/tree/main/skills/review-assumptions
Command: npx skills add https://github.com/Codagent-AI/agent-skills --skill review-assumptions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When implementors complete planned development tasks, they often make unstated risky assumptions or encounter missing context that leads to deviations from the original project plan, undetected bugs, or misaligned features that require costly rework later. This Skill automates the structured review of these assumptions and context gaps to catch issues early, align implementation with intended design, and reduce post-implementation debugging and rework time.

Core Features & Use Cases

  • Structured Finding Tracking: Creates a stable finding ledger to track every assumption and context gap, ensuring no issues are dropped during review.
  • Automated High-Confidence Fixes: Fixes clear deviations from the plan directly in code or docs without requiring user input, reducing manual review work.
  • Clarifying Question Workflow: Presents one ambiguous finding at a time to the user via integrated questioning tools to get precise input without overwhelming them.
  • Context Gap Surfacing: Collects missing plan information from implementor reports to help users update future task generation and specs.
  • Use Case: After an implementor finishes a set of tasks from a software development plan, run this Skill to audit their session reports for unstated assumptions, fix any clear spec deviations, and resolve ambiguous choices with user input to ensure the final implementation matches the original design intent.

Quick Start

Use the review-assumptions skill to audit the latest implementor session reports for your current project's task set and resolve all flagged assumptions and context gaps.

Frequently Asked Questions about review-assumptions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit implementor assumptions from session reports against a project plan?

The skill automates structured review of session reports to track unstated assumptions and context gaps, fixing clear deviations automatically and presenting ambiguous findings one at a time to the user for precise clarification.

How does automated fixing of high-confidence code deviations work during assumption review?

The skill identifies clear deviations from the project plan within session reports and directly fixes high-confidence issues in code or documentation, bypassing the need for manual user intervention to streamline rework.

When do I need to review context gaps and unstated assumptions in software development workflows?

You should review context gaps and unstated assumptions during post-implementation workflows to catch missing plan information early, align implementation with the original design intent, and reduce costly post-implementation debugging or rework.

Can I use session report analysis to surface missing plan information for future task generation?

Yes, session report analysis collects context gaps encountered by implementors to help users update future task generation and specs, ensuring missing plan information is documented and addressed for subsequent development cycles.

What is the best way to resolve ambiguous findings flagged in an implementor audit?

The best way to resolve ambiguous findings is by presenting one clarifying question at a time to the user via integrated questioning tools, soliciting precise input for ambiguous cases without overwhelming the reviewer during the audit.

What are the limitations of automated assumption review for post-implementation code validation?

Limitations include the inability to resolve ambiguous findings without soliciting user input, and the strict requirement for both implementor session reports and the original project plan to verify intent and resolve deviations accurately.