generated from coulomb/repo-seed
- Post-WP-0007 reassessment and SCOPE/README updates - AGENTS.md + workplan-convention task status canon migration - examples/warden.production.example.yaml for production OpenBao - Archive WP-0004 through WP-0007 to workplans/archived/260617-* - WP-0008 T1/T3/T4 done; T2/T5 wait on operator/flex-auth
49 lines
1.9 KiB
Markdown
49 lines
1.9 KiB
Markdown
## Workplan Convention (ADR-001)
|
|
|
|
File location: `workplans/ops-warden-WP-NNNN-<slug>.md`
|
|
ID prefix: `OPS-WP`
|
|
|
|
Work items originate as files in this repo **before** being registered in the hub.
|
|
|
|
Canonical workplan/workstream frontmatter statuses are:
|
|
`proposed`, `ready`, `active`, `blocked`, `backlog`, `finished`, `archived`.
|
|
Use `proposed` for a newly drafted plan, `ready` after review against current
|
|
repo state, and `finished` when implementation is complete. `stalled` and
|
|
`needs_review` are derived health labels, not stored statuses.
|
|
|
|
Closed workplans may be moved to `workplans/archived/` with a completion-date
|
|
prefix: `YYMMDD-ops-warden-WP-NNNN-<slug>.md`. The frontmatter id remains
|
|
unchanged; the prefix is only for quick visual reference.
|
|
|
|
Small opportunistic tasks discovered during another session use **Ad Hoc Tasks**:
|
|
`workplans/ADHOC-YYYY-MM-DD.md`, workstream slug `adhoc-YYYY-MM-DD`, and task ids
|
|
`ADHOC-YYYY-MM-DD-T01`, `T02`, etc. Use adhocs only for low-risk work completed
|
|
directly. Promote anything requiring analysis, design, approval, dependencies, or
|
|
multiple planned phases into a normal workplan.
|
|
|
|
Ecosystem todos from other agents arrive as `[repo:ops-warden]` hub tasks —
|
|
visible at session start. Pick one up by creating the workplan file, then registering
|
|
the workstream.
|
|
|
|
**Task block format** (one per `##` section in workplan files):
|
|
|
|
```
|
|
## Task Title
|
|
|
|
```task
|
|
id: WARDEN-WP-NNNN-T01
|
|
status: wait | todo | progress | done | cancel
|
|
priority: high | medium | low
|
|
state_hub_task_id: "<uuid>" # written by fix-consistency — do not edit
|
|
```
|
|
|
|
Task description text.
|
|
```
|
|
|
|
Canonical task statuses (State Hub InfoTechCanon): `wait`, `todo`, `progress`,
|
|
`done`, `cancel`. Use `wait` for tasks blocked on external dependencies (not
|
|
`blocked` — that alias maps to `wait` during migration). Progression:
|
|
`todo` → `progress` → `done`.
|
|
|
|
<!-- Ralph Loop rules and HEUREKA sequence: ~/.claude/CLAUDE.md — do not duplicate here -->
|