Wayfinder's Recommended Coding Workflow
mattpocockuk · x · 2026-07-11
The author clarified the recommended workflow for /wayfinder:
- /wayfinder → 2. /to-spec → 3. /to-tickets → 4. /implement
The suggestion is to first use /wayfinder to map out the big picture, convert it into a spec, and finally hand it off to an offline execution agent. This allows humans to handle the planning while letting the agent continuously run the implementation autonomously. For non-coding tasks, the author admits /wayfinder can be used as a standalone, end-to-end process.
More from coding & agent
- Soft Clamp cuts tool-call overuse in multi-teacher distillation, from 13.7% to 9.0% — antgroup · 2026-07-21
- SpecJudge runs locally on Ollama to pick the right-sized AI model for your project — jokiruiz · 2026-07-21
- A developer maps out six design rules for CLIs that humans and AI agents can both use — yujiezha · 2026-07-21
- A coding-agent skill that forces ADHD-friendly, answer-first output — ayghri · 2026-07-21
- A set of agent skills for CAD, robotics, and hardware design — earthtojake · 2026-07-21
- Outlines keeps LLMs on-rails with structured outputs — dottxt-ai · 2026-07-21