Direct determines the smallest safe execution contract needed for the user's current request. It preserves the requested outcome and leaves local implementation choices to the executor. It does not create a process record merely because the change is large, and it does not hide intent that should persist merely because the diff is small.
Before performing this skill, references/communication.mdand apply it to natural language sent to readers or stored in documents during execution. This also includes guidance sent when exiting at a gate.
Entry gate
Before performing target-specific actions, references/project-gate.mdand apply the direct row. If the gate routes
elsewhere, change nothing.
If an index is available, read it first. Follow the index route and read only the minimum Product, Domain, Architecture, Design, and decision documents needed to understand this request. Also read the current Git revision and status. Before creating a new artifact, use the index's scoped Work state glob to find whether an already-open result has the same active contract.
If the selected active Work state designated itself as next_route: direct, before judging,
references/work-state.mdand handle only that handoff.
If the handoff requires higher-level judgment or exploration to preserve, keep management of the Work state with direct에 둔 채 next_actionand send the question to the product, architecture, design, adopt or sketchdesignated by
If the current member's Sketch state is next_route가 direct, before writing,
references/sketch-handoff.mdand complete the landing
contract together with the ephemeral instruction or tracked Work publication.
Route questions before writing
First determine whether the request is ready to be directed.
- If product or Domain meaning is lacking, send to
product; if technical boundaries are lacking,architecture; if interaction principles are lacking,design. - If evidence or exploration is needed before even the smallest safe outcome can be determined, write down the governing question and the
evidence that would make it decidable, and return to
sketch. Do not create a Work contract based on speculation. - Ask the user only when a genuinely binding choice remains. Do not ask again for approval of a contract already established by the request and current canon.
Only immediately before actually asking the user's binding choice, references/question-dialogue.mdand apply it to the question
wording.
If the request is ready, check persistence before estimating size. If any of the following yes면 tracked다.
- If the current conversation is interrupted, can the request intent and the next safe action be recovered from the diff alone?
- Does it change durable project knowledge or binding decisions that cannot be safely reflected in the canonical home in the current conversation?
- Are validation, risk, or coordination still open beyond the current conversation, or is an independent verifier needed?
If all are nothen classify the change as ephemeral. Do not create a Work directory. Return the scoped actions to be performed in the current conversation, the necessary canonical reads, write boundaries, proportionate validation, and closure conditions. Do not make a change tracked based only on the number of files and diff size.
If an in-progress ephemeral change crosses this gate, stop before implementing further and reclassify it as tracked.
Apply authorship details only to tracked contracts
After classifying a change as tracked, before composing, creating, or modifying a contract or activating an integration contract,
references/work-state.md와 references/direct-tracked-contract.mdopen. If it ends with only an ephemeral instruction, a return to the owning decision route, or passing the parent question of an existing active Work, do not open tracked authorship details.
Do not modify the spec while another actor holds stewardship. First that actor must next_route: direct, disclose a safe state including the scoped delta and decision question. If stewardship or the current Git baseline is unclear, do not overwrite the contract; stop and send it to user.
If the parent judgment returns to Direct, compare the changed canon against the existing spec and verification. If the contract needs to be reorganized, handle it at the amendment boundary of the tracked authorship details, and if only implementation continues, work, and if the same acceptance must be judged again, verifydisclose the state to.
Return the instruction result
Report the following.
분류:ephemeral,trackedor one owning decision routeArtifacts:Every Work path created or updated, ornone다음 행동:one scoped action per independent artifact. Include integration blocker relationships if any.근거:The canonical documents and Git state used, and the remaining unproven assumptions
It is complete when durability was chosen according to the three questions, each tracked artifact is self-contained and recoverable, only binding choices were escalated, and no implementation or validation was performed. The next actor is the current conversation executor of the ephemeral work, the executable tracked contract's work, the blocked integration or amendment's direct, or one decision route specified above.