decision-gap-scout

Name: decision-gap-scout
Availability: InStock
Author: nanomader

Scan repository docs and extract prioritized unresolved decisions for pre-implementation planning.

1|Updated May 27, 2026

Search Tags:#planning #documentation #decision #risk #gap-analysis #repo-scan #stakeholder-questions

Ready to run

npx skills add https://github.com/nanomader/codex-workflow-skills --skill decision-gap-scout

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decision-gap-scout
Source: https://github.com/nanomader/codex-workflow-skills/tree/main/decision-gap-scout
Command: npx skills add https://github.com/nanomader/codex-workflow-skills --skill decision-gap-scout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface high-priority, unresolved decisions that could derail implementation plans by surfacing gaps in scope, architecture, and requirements.

Core Features & Use Cases

Surface missing decisions from current repo docs and notes during pre-implementation planning.
Produce a concise, prioritized list of decisions and questions that materially affect risk, scope, or rollout.
Use Case: before starting a new feature, run this skill to reveal critical questions about data models, integrations, or security constraints.

Quick Start

Ask the AI to scan the current repo docs and return a concise list of the highest-value unresolved decisions.

Frequently Asked Questions about decision-gap-scout

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

FAQPage Schema

How do I identify unresolved decisions before implementation planning?▼

Identify unresolved decisions by scanning repo docs and notes to surface high-priority gaps in scope, architecture, integrations, data models, testing, and risk. This produces a prioritized list of critical questions that could derail implementation.

When do I need a gap analysis for feature rollout and security constraints?▼

You need a gap analysis during pre-implementation planning to surface missing decisions affecting rollout and security. Scanning documentation extracts unresolved stakeholder questions and architectural gaps before development begins.

What is the best way to find missing decisions in codebase documentation?▼

The best way to find missing decisions is scanning relevant repository docs to extract gaps in data models, integrations, and scope. This returns a compact, prioritized list of high-value unresolved items.

Can I use a repo scan to surface stakeholder questions about architecture and risk?▼

Yes, a repo scan surfaces stakeholder questions by extracting gaps in architecture, risk, and requirements from current documentation. It identifies missing decisions that materially affect project scope.

What limitations exist when scanning docs for missing scope and integration decisions?▼

Scanning docs for missing decisions is limited to analyzing existing repository documentation and notes. It cannot invent new requirements but only exposes unresolved gaps in scope, integrations, and data models already referenced.