Planning and tracking for agent-assisted maintenance work across the PrismarineJS ecosystem (mineflayer, prismarine-* libraries, node-minecraft-protocol, and friends).
This repo holds the thinking behind maintenance work — analysis, plans, and implementation records — as plain Markdown so it can be reviewed, versioned, and picked up by humans or agents.
Work is organized into phases. Each phase has a planning side and an execution side:
design/
phase1/ ← analysis & plans: what's the current state, what should we do
phase2/
...
implementation/
phase1/ ← execution records: what we actually did, decisions, outcomes
phase2/
...
design/phaseN/— Investigation and planning documents. Status reports, triage, proposals, and the rationale for what to work on. Written before the work.implementation/phaseN/— Records of the work itself: what changed, links to the PRs/commits that resulted, decisions made along the way, and follow-ups. Written during/after the work.
A design/phaseN/ document typically motivates one or more
implementation/phaseN/ documents in the same phase.
| Phase | Focus | Design | Implementation |
|---|---|---|---|
| 1 | mineflayer PR backlog triage | design/phase1 | implementation/phase1 |
- One topic per Markdown file; use descriptive
snake_casenames (e.g.mineflayer_pr_status.md). - Lead each document with a short header noting its date and source of data, since status snapshots go stale.
- Keep documents self-contained and link out to the relevant GitHub PRs/issues.