skills.rest
adriaanmostert1976-lab
adriaanmostert1976-labCOMMUNITY
Explore all skills by this author →
GitHub

scope-it

Create structured business requirements documents with guided interview and review modes.

Updated Jun 17, 2026
Search Tags:#project planning#requirements definition#business requirements#scope analysis#startup support
One-click install
npx skills add https://github.com/adriaanmostert1976-lab/adriaan-toolkits --skill scope-it
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scope-it
Source: https://github.com/adriaanmostert1976-lab/adriaan-toolkits/tree/main/business-solution-toolkit/skills/scope-it
Command: npx skills add https://github.com/adriaanmostert1976-lab/adriaan-toolkits --skill scope-it

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The skill tackles the challenge of defining business requirements when ideas are unclear or when stakeholders have half-formed ideas.

Core Features & Use Cases

  • Structured Requirements: Transforms vague ideas into detailed business requirements documents.
  • Interviewer Mode: Guided questions to refine problem statements, user scenarios, and success criteria.
  • Reviewer Mode: Critique existing briefs and identify gaps in scope and requirements.
  • Revision Mode: Adjust requirements when the project scope changes post-initial assessment.
  • Use Case: For a startup planning to build a new product, use the skill to articulate the problem, target users, and desired outcomes before designing the solution.

Quick Start

To initiate a new business requirements analysis, type: "start new scope analysis for our product project".

Frequently Asked Questions about scope-it

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

FAQPage Schema
How do I structure business requirements when the project idea is still fuzzy?▼

To structure business requirements from fuzzy ideas, use a guided interviewer mode that asks targeted questions to refine problem statements, define user scenarios, and establish clear success criteria.

What is the best way to define scope boundaries for a new startup product?▼

The best way to define scope boundaries for a startup product is to articulate the problem, target users, and desired outcomes in a structured brief before designing the actual solution.

Can I critique an existing business requirements document to find scope gaps?▼

Yes, you can use a reviewer mode to critique existing briefs, specifically identifying gaps in scope and requirements to ensure your project boundaries remain accurate and complete.

How do I adjust project scope when requirements change after the initial assessment?▼

You can adjust project scope using a revision mode, which allows you to modify and update requirements documents when the project scope evolves or changes post-initial assessment.

Does scope analysis require structured input to function optimally?▼

Yes, scope analysis requires interaction and structured input to function optimally, ensuring the resulting business requirements document accurately captures the problem space and user value.

Related Skills

Explore More Product & Management Skills→
aaronbassettaaronbassett
4

ideas:ideation

Transform vague project ideas into structured vision documents with defined scope.

Community
Advanced
farmountainfarmountain
1

Backlog Manager Agent

Prioritize product backlog items and generate sprint plans from capacity data.

Community
Advanced
rafazshrafazsh

project-planner

Break down complex projects into tasks, timelines, dependencies, and milestones.

Community
Intermediate
fearovexfearovex

requirements-architect

Define software requirements and architecture using structured templates.

Community
Advanced