Hmbown Step Sword
Close the gap and cut in one motion.
Overview
Use Step Sword when the target is identifiable but not within easy reach: you know exactly what needs cutting, but reaching it requires navigating across files, modules, or abstraction layers. Warp directly to the target and make the edit in a single committed action.
This is the secondary Codex compatibility rendering of a metaphorical battle-chip pattern with a shipping-now execution model.
Canonical chip family: Step Sword Codex shelf: Direct Fire and Breach Provider target: Codex compatibility surface.
When To Use
- You can name the exact remote location that needs editing but it is not adjacent to your current context.
- The problem is well-scoped but buried behind layers of indirection or deep file paths.
- Traversing the full path step by step would waste rounds; the target is clear enough to strike immediately.
Workflow
- Identify the remote target precisely — file path, line range, symbol — so the warp lands cleanly.
- Jump directly to the target context and cut in the same motion.
- Verify the strike from both ends: confirm the edit is correct and that no caller or dependant was sheared.
Deliverables
- A precise remote edit made by direct navigation, not incremental traversal.
- A short note confirming the warp destination and what was left untouched along the path.
Guardrails
- Do not use Step Sword if you cannot name the target precisely — vague warp destinations cause collateral cuts.
- If the path to the target contains other problems that should be addressed first, use a room-control chip instead.
- Do not chain Step Swords to simulate traversal; that is a sign the wrong chip is equipped.
Default Invocation
Use Step Sword to warp directly to the identified remote target and make the precise edit in one committed action, then verify that the change is correct and nothing along the path was disturbed.