skills.rest
vmobifystudio
vmobifystudioCOMMUNITY
Explore all skills by this author →
GitHub

spec-critic

Review sprint tickets and implementation specifications for ambiguities before development.

4|Updated Jun 1, 2026
Search Tags:#edge cases#acceptance criteria#sprint planning#requirements validation#specification review#ambiguity detection#developer handoff
One-click install
npx skills add https://github.com/vmobifystudio/app-dev-team --skill spec-critic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-critic
Source: https://github.com/vmobifystudio/app-dev-team/tree/main/skills/spec-critic
Command: npx skills add https://github.com/vmobifystudio/app-dev-team --skill spec-critic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents developers from guessing about ambiguous implementation details that would otherwise cause rework, defects, and inconsistent behavior.

Core Features & Use Cases

  • Acceptance-Criteria Review: Examines every sprint ticket and its implementation specification for unresolved decisions.
  • Edge-Case Detection: Identifies missing error types, empty and failure states, cancellation behavior, source-of-truth rules, validation ownership, units, offline behavior, idempotency, and atomicity.
  • Ledger-Based Resolution: Files concise, ticket-specific questions for the technical lead and ensures answers are folded back into the implementation specifications before development begins.
  • Use Case: Before launching a sprint for a mobile app, use this Skill to expose unclear photo-picker cancellation behavior, repository error mapping, or unspecified empty-state copy.

Quick Start

Ask the spec-critic skill to review the sprint board and implementation specifications for developer-blocking ambiguities before any developer is spawned.

Frequently Asked Questions about spec-critic

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

FAQPage Schema
How do I find ambiguities in technical specifications before sprint planning?▼

To find ambiguities in technical specifications, review sprint tickets and acceptance criteria for unresolved decisions like missing error types, empty states, and validation ownership. This exposes gaps before developer handoff, preventing rework.

What edge cases should I check for when reviewing implementation specifications?▼

When reviewing implementation specifications, check for missing error types, empty and failure states, cancellation behavior, source-of-truth rules, validation ownership, units, offline behavior, idempotency, and atomicity to ensure complete requirements validation.

How do I track unresolved specification questions for a technical lead?▼

Track unresolved specification questions by creating a ticket-specific ledger with capped findings and owner-routed entries. This routes questions directly to the technical lead and ensures answers are folded back into the specifications.

Does requirements validation work for mobile app sprint tickets?▼

Requirements validation works for mobile app sprint tickets by identifying unspecified behaviors like photo-picker cancellation or repository error mapping. It exposes missing decisions in acceptance criteria before development begins.

What is the best way to prevent developers from guessing on missing acceptance criteria?▼

The best way to prevent developers from guessing on missing acceptance criteria is to perform a specification review that detects ambiguities and routes ticket-grounded questions to the technical lead. Answers are then folded back into the spec.

Related Skills

Explore More Software Engineering Skills→
fieldspherefieldsphere
37

write-ticket

Draft implementation-ready tickets with structured sections from product requests or incidents.

Official
Intermediate
brianruggieribrianruggieri

grill-me

Analyze plans by interrogating decision branches and generating a structured decision log.

Community
Advanced
ianshankianshank
1

dev-sqe-handoff

...

Community
Advanced
IoT-VNIoT-VN

code-review

Review code for technical correctness and edge cases before pull requests.

Community
Advanced