skills.rest
PaulCrossland1
PaulCrossland1COMMUNITY
Explore all skills by this author →
GitHub

001-scope-project

Guide iterative discovery questions to structure software requirements and generate PRD-ready outlines.

Updated Aug 23, 2026
Search Tags:#requirements#discovery#PRD#scope#workflows#stakeholders
One-click install
npx skills add https://github.com/PaulCrossland1/claude-code-skills --skill 001-scope-project
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 001-scope-project
Source: https://github.com/PaulCrossland1/claude-code-skills/tree/main/001-scope-project
Command: npx skills add https://github.com/PaulCrossland1/claude-code-skills --skill 001-scope-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams and engineers scope software projects by guiding iterative discovery. It enables capturing requirements, workflows, risks, and success criteria before execution, reducing ambiguity and rework.

Core Features & Use Cases

  • Structured questioning to extract requirements across project types (new products, feature expansions, audits, migrations)
  • Step-by-step guidance with confirmation points to align stakeholders
  • Generates a concise PRD-ready outline from gathered inputs

Quick Start

Start a discovery session by outlining the high-level goal and any known constraints, then answer guided prompts to flesh out scope.

Frequently Asked Questions about 001-scope-project

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

FAQPage Schema
How do I scope software project requirements before writing a PRD?▼

To scope software project requirements before a PRD, use structured discovery questioning to iteratively extract workflows, constraints, and success criteria from stakeholders. This reduces ambiguity and captures necessary inputs before execution.

What is the best way to gather stakeholder requirements for feature enhancements?▼

The best way to gather stakeholder requirements for feature enhancements is through iterative discovery prompts with confirmation points. This step-by-step guidance aligns stakeholders and enforces a consistent data model for tech decisions.

Can I use structured discovery workflows for security audits and migrations?▼

Yes, structured discovery workflows support a broad range of use cases including security audits and migrations. Targeted prompts guide you through extracting requirements and constraints specific to these project types.

How do I generate a PRD-ready outline from gathered project scope data?▼

You generate a PRD-ready outline by feeding gathered inputs—such as success criteria, stakeholders, and workflows—into a structured data model. This enforces consistency and produces a concise outline for product requirements documentation.

When do I need iterative discovery questions for product launches?▼

You need iterative discovery questions for product launches when you must capture unknown workflows, risks, and tech decisions upfront. Structured prompts with confirmation steps reduce rework by aligning stakeholders before execution begins.

Related Skills

Explore More Product & Management Skills→
velcraftingvelcrafting
1

intake-interview

Interview stakeholders to generate a structured Intake Brief with bounded questions.

Community
Intermediate
elsolalelsolal
1

architect

Generate an architecture blueprint with stack decisions and module boundaries from a PRD.

Community
Advanced
librefanglibrefang
10

project-manager

Plans and guides software projects using Agile principles and structured frameworks.

Official
Advanced
Andy-HNUAndy-HNU

writing-prds

Capture and organize product requirements into actionable PRDs.

Community
Intermediate