docs: add execution roadmap workflow
This commit is contained in:
@@ -0,0 +1,61 @@
|
||||
# Add Execution Roadmap Workflow
|
||||
|
||||
## Status
|
||||
|
||||
- `completed`
|
||||
|
||||
## Owner
|
||||
|
||||
- codex
|
||||
|
||||
## Started At
|
||||
|
||||
- `2026-03-19`
|
||||
|
||||
## Goal
|
||||
|
||||
- introduce a repository-level execution-roadmap workflow so substantial agent work leaves a durable trace while active and a completion record after archiving
|
||||
|
||||
## Scope
|
||||
|
||||
- update `AGENTS.md` with active/archive roadmap rules
|
||||
- create `docs/roadmaps/README.md`
|
||||
- create `docs/roadmaps/TEMPLATE.md`
|
||||
- create tracked `active/` and `archive/` directories
|
||||
- update `docs/implementation-roadmap.md`
|
||||
|
||||
## Checklist
|
||||
|
||||
- [x] define the execution-roadmap workflow and naming rules
|
||||
- [x] update `AGENTS.md` to require active roadmap files for substantial multi-step work
|
||||
- [x] add `docs/roadmaps/README.md`
|
||||
- [x] add `docs/roadmaps/TEMPLATE.md`
|
||||
- [x] create tracked `docs/roadmaps/active/` and `docs/roadmaps/archive/`
|
||||
- [x] update `docs/implementation-roadmap.md`
|
||||
|
||||
## Files
|
||||
|
||||
- `AGENTS.md`
|
||||
- `docs/roadmaps/README.md`
|
||||
- `docs/roadmaps/TEMPLATE.md`
|
||||
- `docs/roadmaps/active/.gitkeep`
|
||||
- `docs/roadmaps/archive/.gitkeep`
|
||||
- `docs/implementation-roadmap.md`
|
||||
|
||||
## Decisions
|
||||
|
||||
- use `docs/roadmaps/active/` and `docs/roadmaps/archive/` rather than a single mixed directory
|
||||
- keep project-level roadmaps separate from per-workstream execution traces
|
||||
- require one roadmap file per substantial workstream rather than one file per tiny action
|
||||
|
||||
## Blockers
|
||||
|
||||
- none
|
||||
|
||||
## Next Step
|
||||
|
||||
- use `docs/roadmaps/TEMPLATE.md` as the starting point for the next substantial multi-step task
|
||||
|
||||
## Completion Summary
|
||||
|
||||
- the repository now has a documented execution-roadmap workflow, tracked directories for active and archived workstreams, and a reusable template for future agents
|
||||
Reference in New Issue
Block a user