68 lines
2.7 KiB
Markdown
68 lines
2.7 KiB
Markdown
# [Game Title] — Tasks
|
|
|
|
Project Version: v0.1.0
|
|
Document Revision: 1
|
|
Last Updated By: <stable-agent-id>
|
|
|
|
> Every Agent reads and maintains this current-version task context. Keep specialized facts in role-owned artifacts and link them here. Record owner, status, acceptance, evidence, blockers, version proposals, and next action.
|
|
|
|
## Now
|
|
|
|
### TASK-001 — [Player-visible outcome]
|
|
|
|
- **Design source:** [§ exact GDD heading, SYS-###, or concise defect note]
|
|
- **Why now:** [Risk reduced, loop completed, or evidence needed]
|
|
- **Playable slice:** [Start condition → player action → feedback/result → retry/continue]
|
|
|
|
#### Acceptance criteria — 1 to 3
|
|
|
|
- [ ] [Observable behavior in the target play environment]
|
|
- [ ] [Critical rule, failure, or edge case]
|
|
- [ ] [Feedback, recovery, or complete-loop condition]
|
|
|
|
#### Non-goals — maximum 3
|
|
|
|
- [Behavior, content, or polish explicitly outside this task]
|
|
- [Optional exclusion]
|
|
- [Optional exclusion]
|
|
|
|
#### Completion evidence — 1 to 3
|
|
|
|
- [ ] [Build/test command and result]
|
|
- [ ] [Playtest path and observed result]
|
|
- [ ] [Optional screenshot, recording, log, or URL]
|
|
|
|
## Next — maximum 3
|
|
|
|
1. **TASK-002 — [Player-visible outcome]** — Design: [§ heading/SYS-###/defect note] — [Why it follows]
|
|
2. **TASK-003 — [Player-visible outcome]** — Design: [§ heading/SYS-###/defect note] — [Why it follows]
|
|
3. **TASK-004 — [Player-visible outcome]** — Design: [§ heading/SYS-###/defect note] — [Why it follows]
|
|
|
|
## Blocked
|
|
|
|
| Task | Design reference | Blocker | Evidence already gathered | Unblock condition/owner |
|
|
|---|---|---|---|---|
|
|
| [TASK-### — outcome] | [§ heading/SYS-###] | [Specific missing input or dependency] | [Link/result] | [Concrete condition and responsible person if known] |
|
|
|
|
## Version Proposals
|
|
|
|
| Proposed version | Level | Proposed by | Reason | Affected artifacts | Status |
|
|
|---|---|---|---|---|---|
|
|
| [v0.2.0] | [PATCH/MINOR/MAJOR] | [stable-agent-id] | [Why a new version is needed] | [Files/areas] | proposed |
|
|
|
|
## Last verified
|
|
|
|
- **Date/build:** [YYYY-MM-DD + URL/tag/commit]
|
|
- **Environment:** [Device, browser/runtime, display, and input]
|
|
- **Verified path:** [Start → core action → result → retry/continue]
|
|
- **Checks passed:** [Build/runtime/console/playtest results]
|
|
- **Known issue:** [Most important remaining issue, or “None known”]
|
|
|
|
## Promotion rule
|
|
|
|
When `Now` is complete:
|
|
|
|
1. Record up to three pieces of completion evidence and update `Last verified`.
|
|
2. Propagate any design discovery to the applicable GDD section or defect note before closing the task.
|
|
3. Promote at most one `Next` task that attacks the largest current risk or closes the most important playable loop. If none is justified, leave `Now` explicitly empty.
|