Surface underspecified acceptance criteria and scope gaps in GitHub issues and plan files.
npx skills add https://github.com/mfittko/dev-loops --skill loop-grill
Please help me install this Agent Skill. Skill: loop-grill Source: https://github.com/mfittko/dev-loops/tree/main/.claude/skills/loop-grill Command: npx skills add https://github.com/mfittko/dev-loops --skill loop-grill
Dev loops often stall or require rework when GitHub issues or local plan files lack clear acceptance criteria, defined scope boundaries, identified primary actors, or documentation of irreversible decisions. This Skill surfaces these underspecified gaps before implementation begins, reducing wasted effort and rework.
Use the loop-grill skill to run a pre-loop gap check on GitHub issue 42 or your local feature plan file.
High-intent search queries and answers about installing and using this skill.
Pre-loop gap detection surfaces missing acceptance criteria in GitHub issues before development starts. It analyzes issue text to identify fuzzy scope boundaries, unresolved primary actors, and undocumented irreversible decisions to prevent wasted effort.
Auditing local plan files for underspecified scope boundaries involves checking for unresolved primary actors and undocumented hard-to-reverse decisions. This pre-loop review process highlights gaps in feature plans to reduce implementation rework.
Auto-answer mode resolves spec gaps automatically by pulling evidence from your codebase, project documentation, and repository context. This bypasses interactive Socratic Q&A to provide gap resolution without manual human prompting.
Socratic Q&A for clarifying undocumented irreversible decisions uses interactive questioning to guide human-led clarification. It prompts the user to resolve underspecified criteria and scope boundaries found during the plan validation process.
Writing grill findings back to GitHub issues uses replace-section semantics to ensure idempotent re-runs. This structured write-back approach includes guards that prevent duplicate sections when gap checks are executed multiple times.
Plan validation for a development loop is needed when GitHub issues or local plan files lack clear acceptance criteria, defined scope boundaries, or identified primary actors. Running pre-loop reviews prevents dev loops from stalling.
nq-rdlConvert task lists into dependency-ordered GitHub issues from design artifacts.
bacchus-labsTrace specification requirements through implementation artifacts and compliance checks.
DeL-TaiseiOzakiDetect tech stack and commands from project files to update AGENTS.md top sections.
silaslopes100Identify and resolve ambiguities in project requirement documents through gap analysis and user questioning.
