review-question

Reviews question records for specificity, answerability, impact, and resolution quality.

11|1|Updated Jul 25, 2025
Ready to run
npx skills add https://github.com/tomzx/agents --skill review-question-tomzx
💬 Prompt for ChatGPT / Claude Chat▼
Please help me install this Agent Skill.
Skill: review-question
Source: https://github.com/tomzx/agents/tree/main/skills/review-question
Command: npx skills add https://github.com/tomzx/agents --skill review-question-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open questions in a software project often stay vague, unassigned, or unresolved, blocking decisions and work. This Skill audits a question record against a structured checklist so gaps in specificity, context, answerability, impact, and resolution quality are surfaced and the record's lifecycle status is updated consistently. ## Core Features & Use Cases - Five-Category Audit: Evaluates a question document across specificity, context, answerability, impact and urgency, and resolution quality, omitting categories with no findings. - Lifecycle Status Management: Sets the frontmatter status to Resolved, Deferred, or Dismissed based on the review outcome, and records answers in the Answer section. - Structured Verdict Output: Emits an approved, changes-requested, or rejected verdict to $OUTCOME_YAML following shared SDLC conventions. - Use Case: A question record says "what about compliance?" with no scope. The review flags it under Specificity and proposes a restatement a named source could answer directly, such as whether EU user data requires residency guarantees under the current data processing agreement. ## Quick Start Review the question record at .sdlc/knowledge/questions/3-auth-timeout.md and update its status based on the findings.

Frequently Asked Questions about review-question

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

FAQPage Schema
How do I review an open question record in an SDLC workflow?▼

Provide the question document or its file path, and the record is evaluated against a five-category checklist covering specificity, context, answerability, impact, and resolution quality. Findings are reported by category and the frontmatter status is updated to Resolved, Deferred, or Dismissed.

What makes a question record answerable?▼

An answerable question names a concrete scope, identifies an answerer such as a person, team, or vendor, or cites an authoritative source like a document or experiment. It should also describe the channel or method for obtaining the answer.

What status values can a question record have?▼

A question record can be Open, Resolved, Deferred, or Dismissed. Resolved means the answer is recorded in the Answer section, Deferred means it cannot be answered yet with a revisit date set, and Dismissed means it is no longer relevant with a reason recorded.

When should a question be promoted to an assumption or decision?▼

If work proceeds on an unverified answer, the question should be promoted via /create-assumption and linked. If the answer requires choosing between options, the decision should be recorded via /create-decision and linked from the question record.

What verdicts does the question review produce?▼

The review emits one of three verdicts to $OUTCOME_YAML: approved when there are no blocking findings, changes-requested when the author must address findings, and rejected when a fundamental flaw requires rework. Changed records are listed under artifacts.