27 lines
985 B
Markdown
27 lines
985 B
Markdown
# Session Start Workflow
|
|
|
|
## Purpose
|
|
Start each implementation session with correct scope, context, and task state before editing files.
|
|
|
|
## Inputs
|
|
- Current priority task from Archon.
|
|
- Governance docs in `docs/00-governance/`.
|
|
|
|
## Steps
|
|
1. Open and read in order:
|
|
- `docs/00-governance/executive_summary.md`
|
|
- `docs/00-governance/current_status.md`
|
|
- `docs/00-governance/active_work.md`
|
|
- `docs/00-governance/architecture.md`
|
|
- `docs/00-governance/roadmap.md`
|
|
2. Pull current task details from Archon and confirm acceptance criteria.
|
|
3. Confirm allowed file scope from task spec and `.kilocode/rules/file_boundaries.md`.
|
|
4. Move task status in Archon from `todo` to `doing`.
|
|
5. Capture a short execution plan (3-6 bullets) tied to acceptance criteria.
|
|
6. Begin implementation with minimum-diff edits only in scoped files.
|
|
|
|
## Exit Criteria
|
|
- Task is set to `doing`.
|
|
- Scope boundaries are explicitly confirmed.
|
|
- Work plan exists and maps to task acceptance criteria.
|