scope

Create structured product specs with frontmatter and template references.

232|43|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/whawkinsiv/solo-founder-superpowers --skill scope-whawkinsiv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope
Source: https://github.com/whawkinsiv/solo-founder-superpowers/tree/main/developer-skills/1-scope
Command: npx skills add https://github.com/whawkinsiv/solo-founder-superpowers --skill scope-whawkinsiv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn vague ideas into clear, buildable specs for AI tools or stakeholders. Use when starting features, planning projects, or when AI keeps building the wrong thing. Creates Quick Feature Specs (10-15 min) for immediate AI builds or Full Project Scopes (1-2 hours) for budget planning and contractor estimates.

Core Features & Use Cases

  • Quick Feature Spec (10-15 min): ideal for single features, iterations, or additions that you can hand to AI tools to generate artifacts.
  • Full Project Scope (1-2 hours): for major releases and stakeholder review, including milestones, tasks, risks, and budgets.
  • Use Case: Aligns teams and sets clear expectations before build.

Quick Start

Create either a Quick Feature Spec or a Full Project Scope using the templates in QUICK-SPEC.md and PROJECT-SCOPE.md to begin.

Frequently Asked Questions about scope

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

FAQPage Schema
What is a project scope document and when do I need a full spec versus a quick feature spec?

A project scope document defines buildable specifications for stakeholders or AI tools. You need a quick feature spec for single AI-generated features, and a full project scope for major releases requiring budget planning and contractor estimates.

How do I turn a vague product idea into a buildable spec for AI tools?

To turn a vague idea into a buildable spec, use structured templates like QUICK-SPEC.md or PROJECT-SCOPE.md. This process translates abstract concepts into clear documentation with required frontmatter, ensuring AI tools build the correct artifacts.

Why does AI keep building the wrong feature and how can project scoping fix it?

AI builds the wrong feature when project scoping lacks clear boundaries and structured documentation. Correcting AI misconceptions during scoping ensures the generated specifications include explicit references and required frontmatter to guide the build accurately.

Can I use these specification templates for stakeholder review and budget planning?

Yes, you can use the Full Project Scope templates for stakeholder review and budget planning. This structured documentation includes milestones, tasks, and risks, aligning teams and setting clear expectations before the build phase begins.

What is the best way to document project scope for contractor estimates?

The best way to document project scope for contractor estimates is creating a Full Project Scope. This structured specification details milestones, tasks, and risks, providing contractors with the clear buildable parameters needed for accurate budget estimates.

Are there limitations to using quick feature specs for major project releases?

Yes, quick feature specs are limited to single features or iterations for immediate AI builds. Major project releases require a Full Project Scope to properly document milestones, tasks, and risks for stakeholder alignment and budget planning.