scope-analyst

Analyze project scope and output intent classification, findings, questions, risks, and recommendations.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/giwa/codex-helper --skill scope-analyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-analyst
Source: https://github.com/giwa/codex-helper/tree/main/skills/scope-analyst
Command: npx skills add https://github.com/giwa/codex-helper --skill scope-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams analyze and clarify project scope before planning to prevent miscommunication and misalignment.

Core Features & Use Cases

  • Classifies intent and identifies ambiguities early in the pre-project phase.
  • Surface hidden requirements, risks, and dependencies to guide decision making.
  • Produces a structured output including an intent classification, findings, questions, risks (with mitigations), and a recommended course of action.

Quick Start

Provide a clear project request to the Scope Analyst and obtain a structured scope analysis ready for preplanning.

Frequently Asked Questions about scope-analyst

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

FAQPage Schema
How do I clarify project scope before planning to prevent misalignment?

Use a preplanning scope analysis to classify project intent, surface hidden requirements, and identify ambiguities. This process outputs structured findings, targeted questions, and risk mitigations to ensure stakeholder alignment before planning begins.

What is the best way to identify risks in complex project integrations during discovery?

Analyzing project scope during pre-project discovery identifies risks in complex integrations by evaluating ambiguous stakeholder expectations. It outputs a structured assessment of risks paired with specific mitigations to guide decision making.

How do I analyze unclear requirements before starting a project?

Provide the raw project request for scope evaluation to analyze unclear requirements. The analysis classifies intent and highlights ambiguities, producing structured findings and questions to resolve gaps before planning proceeds.

Can I get a recommendation on whether to proceed or revisit scope for ambiguous stakeholder expectations?

Yes, scope analysis evaluates ambiguous stakeholder expectations during pre-project discovery and outputs a clear recommendation. This recommendation advises whether to proceed with planning or revisit the scope to prevent miscommunication.

What limitations exist when analyzing scope for complex integrations?

Scope analysis relies on the initial project request quality to identify risks and ambiguities for complex integrations. If input requirements lack detail, the resulting intent classification and findings may require further stakeholder clarification.