Step 1 · Define Product Scope

Goal

Define the product scope, requirements, and high-level architecture before starting development.

Instructions

You are in workflow step 1 of the scope-cycle. Your goal is to analyse the project and define a clear product scope.

Tasks to perform

1. Analyse Existing Code

  • Review the current codebase structure.
  • Identify existing features and functionality.
  • Document technical stack and dependencies.

2. Define Product Scope

  • What is the core purpose of this product?
  • What features are in scope for the current phase?
  • What features are explicitly out of scope?
  • Who are the target users?

3. Technical Architecture

  • Document the high-level architecture.
  • Identify key components and services.
  • Define data models and relationships.
  • Document external integrations.

4. Requirements Gathering

  • Functional requirements.
  • Non-functional requirements (performance, security, scalability).
  • Technical constraints.
  • Dependencies on external systems.

5. Create Scope Document

  • Write a comprehensive SCOPE.md file in the project root.
  • Include product vision, features, architecture, and requirements.
  • Document assumptions and constraints.

Expected Output

After completing this workflow step, you should have created:

  • SCOPE.md — complete product scope definition.
  • TODO.md — with a single verification task.

Example TODO.md output

## Todo
- [ ] verify: Product scope documented in SCOPE.md, ready to proceed to planning phase _(ref: workflows/scope-cycle/01-define-product-scope.md)_

TODO status rules: [ ] = not started · [~] = in progress (one at a time) · [x] = done (prefix the date). Always include _(ref: workflows/scope-cycle/01-define-product-scope.md)_ on every task written by this step.

SCOPE.md template

# Product Scope

## Vision
[What is the product's purpose and vision?]

## Target Users
[Who will use this product?]

## In Scope
[Features included in this phase]

## Out of Scope
[Features explicitly excluded]

## Technical Stack
[Languages, frameworks, databases, services]

## Architecture
[High-level component diagram or description]

## Requirements
### Functional
- [Requirement 1]

### Non-Functional
- [Performance targets]
- [Security requirements]
- [Scalability considerations]

## Assumptions & Constraints
[What are we assuming? What are we constrained by?]

Exit Criteria

This workflow step is complete when:

  • SCOPE.md has been created with all sections filled in.
  • TODO.md has a verification task.
  • You have committed both files.