Work

Overview

/work is the main developer skill. It consumes the exploration contract produced by /explore and turns it into shipped code — without re-deciding scope, re-discovering the pattern, or widening the blast radius.

Core principle: The exploration report is the contract. Implementation follows the contract. If the contract is wrong or insufficient, stop and update the contract — do not improvise in code.

Design goals every change must optimize for:

• Contract adherence — every edited file and line traces to §7 Proposed Changes in the explore report
• High cohesion, low coupling — one concern per change, no cross-module drive-bys
• Reuse over duplication — prefer existing utilities/DTOs/services; justify every new item inline
• Minimal blast radius — touch only what the report listed; surface anything else as a blocker
• Style match — follow the patterns the report cited, even if you'd personally do it differently

Violating the letter of this process is violating the spirit. A clever refactor that wasn't in the report is not professionalism; it's scope creep.

The Iron Law