spec-developlisted

# OpenSpec Apply (Task Execution) Guide for implementing code changes driven by `tasks.md`. ## Input Files | File | Purpose | Action | |------|---------|--------| | `{specs_path}/tasks.md` | Implementation checklist | Read, execute, mark done | | `{specs_path}/design.md` | Architecture decisions | Reference during implementation | | `{specs_path}/proposal.md` | Context and motivation | Reference if unclear on intent | **Path Enforcement**: The `specs_path` MUST be `.scaffolding/conversations/{UUID}/specs/` where `{UUID}` is a valid UUID (format: `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`). NEVER use descriptive folder names. ## Execution Protocol ### Step 1: Read tasks.md Parse all task groups and checkboxes. Identify dependency order. ### Step 2: Execute tasks in order For each task (`- [ ] N.M description`): 1. Read the task description and target file path 2. Check design.md for relevant requirements and decisions 3. Implement the change following project patterns 4. Mark complete: change `- [ ]` to `- [x]` ### Step 3: Run validation after each group | Stack | Validation Command | |-------|--------------------| | Backend | `pytest` | | Frontend | `npm run validate` | | Both | Run both commands | ### Step 4: Handle blockers If a task cannot be completed: ```markdown - [ ] 2.3 Implement caching layer > BLOCKED: Redis connection config not yet available. Depends on devops setup. ``` Continue with unblocked tasks. Do not stop the entire chain. ## Rules | Rule |