arrow_backBack to Tools
description
Cycle Doc Generator
Fill in scopes, decisions and weeks β get a ready-to-drop Shape-Up-style cycle doc as Markdown.
planningmarkdown
/ Scopes
/ Decision log
No decisions yet. Template row will show in output.
/ Output
Β·
Cycle 01
Scopes
-
Scope A (
SCOPE A)Goal
<TBD>User Flow
- <TBD>
Dependencies
- <TBD>
Definition of Done
- <TBD>
Risks / Unknowns & Open Questions
- <TBD>
-
Scope B (
SCOPE B)Goal
<TBD>User Flow
- <TBD>
Dependencies
- <TBD>
Definition of Done
- <TBD>
Risks / Unknowns & Open Questions
- <TBD>
-
π§± Template
Goal
<TBD>User Flow
- <TBD>
- <TBD>
Dependencies
- <TBD>
Definition of Done
<TBD>Risks / Unknowns & Open Questions
- <TBD>
π¦Control Panel
| Scope | Status | Epic |
|---|---|---|
SCOPE A | Uphill | <Github Link> |
SCOPE B | Uphill | <Github Link> |
ποΈ Decision Log
| Date | Scope(s) | Decision |
|---|---|---|
| <DATE> | SCOPE A | (Owner @person) <TBD> |
πͺ Progress Review
[List of high-level work completed - organised by scope]
- Week 1
SCOPE A- <Details>
SCOPE B- <Details>
- Week 2
SCOPE A- <Details>
SCOPE B- <Details>
- Week 3
SCOPE A- <Details>
SCOPE B- <Details>
- Week 4
SCOPE A- <Details>
SCOPE B- <Details>
- Week 5
SCOPE A- <Details>
SCOPE B- <Details>
- Week 6
SCOPE A- <Details>
SCOPE B- <Details>
π§ Road Blocks
[List any issues, side-quests, unexpected work, blockers, or relevant details that have affected the cycle's delivery - e.g. Week 2: CI Down causing delays in merging code]
π― Confidence Level
[Define a value between 1 and 10 that signifies the confidence that we will ship on target - the ideal confidence value is something that trends upward as the weeks go by]
- Week 1:
- Week 2:
- Week 3:
- Week 4:
- Week 5:
- Week 6:
Runs entirely in your browser. Nothing is sent anywhere.