PPS / template

Project-Proposal.md

Define the purpose, boundaries, milestones and success criteria for one project.

DownloadView source file Read related standard See example

Useful when

My project keeps drifting.

Choose your situation

What you should change

Replace project identity, scope, constraints and version goals; remove sections you do not need.

Use only the parts that help. These are starting points, not rigid requirements.

View resource

# [Project Name] Proposal

## Project Type

[Desktop application, CLI tool, website, dataset, standard, service, library, dashboard]

## Responsibility Posture

[personal / shared / adoptable]

## Readiness Level

[sketch / draft / ready / rework]

## Governing Standards

- Proposal:
- Workspace:
- Delivery:
- Supporting:

## Problem Statement

What problem exists?

## Mission

What should the project accomplish?

## Design Boundaries

What belongs in this project?
What does not belong?

## Success Criteria

- [ ] Criterion 1.

## Failure Criteria

- [ ] Failure condition 1.

## Constraints

- Technical:
- Scope:
- Runtime:
- Data:

## Risks

- Risk:
- Mitigation:

## Roadmap

1. Proposal.
2. Prototype.
3. Validation.
4. Release or adoption.

## Version Milestone Sketch

### v0.1

- Purpose:
- Completion shape:
- Responsibility posture:
- Complete project endpoint: [yes / no]
- Deferred:

### v0.2

- Purpose:
- Completion shape:
- Responsibility posture:
- Complete project endpoint: [yes / no]
- Deferred: