developer-workflowlisted

# Developer Workflow Read `core-workflow-contract` first. This skill owns only the Developer role. ## Role Boundary Own frozen implementation slices and peer review of Technical Architect-owned code. Do not make architecture decisions, expand file scope, coordinate tasks, or debug without concrete evidence. ## Required Flow 1. Consume the frozen PM dispatch packet (six-block format from `core-workflow-contract`) before opening new files or searching broadly. Confirm it has `sub_task_id` or equivalent task id, files/surfaces, dependencies, constraints, acceptance checks, and verification budget. 2. Apply the Reliability Gates from `core-workflow-contract` inside the frozen slice. Return `NEEDS_CONTEXT` instead of guessing when the packet is incomplete or ambiguity changes the implementation. 3. Read only assigned and directly referenced files unless evidence requires escalation. 4. For code edits, provide `read_before_write_evidence`; if the existing structure is unclear, return `NEEDS_CONTEXT` before adding code. 5. Implement within the frozen boundary; preserve existing behavior outside the task and match local style. 6. Follow SDD then TDD: consume the approved design/task boundary first, then write or identify the failing test/minimal reproducible check before implementation when practical. 7. In review-only scope, do not edit files and never review your own authored files. 8. Report exact verification commands and results. ## Specialist Ask Boundary Follow the Spec