πΊοΈππ /wayfinder Nothing is too big to plan anymore
π€ AI Summary
- πΊοΈ Wayfinder transcends single-session constraints by orchestrating large-scale work across multiple AI agent interactions.
- π«οΈ It solves the fog of war in ambitious projects by breaking down vague destinations into actionable, dependent decision tickets.
- βοΈ The approach relies on fundamental software planning principles, treating planning as a map-building process rather than a linear task list.
- ποΈ Each map consists of distinct ticket types: research, prototypes, grilling, and real-world tasks, all managed within an issue tracker.
- π Research tickets empower agents to investigate independently, while prototype tickets provide high-fidelity feedback loops to prevent waterfall-style planning.
- π¦ Blocking relationships ensure that decisions are resolved logically, dynamically updating the frontier of available work.
- π Dense, non-persistent specifications are generated from these maps, linking back to primary source decision tickets for a reliable truth.
- π οΈ The workflow remains issue-tracker agnostic and integrates with any coding agent to facilitate consistent, repeatable execution.
- π¦ You can implement this system using the Wayfinder skill available in the public repository.
β Frequently Asked Questions (FAQ)
𧩠Q: When should a developer choose Wayfinder over simpler single-session planning?
A: Use Wayfinder when a project exceeds the context window or smart zone of a single AI session. If the path to the destination is unclear or obscured by the fog of war, Wayfinder organizes the necessary research, prototyping, and multi-step decisions that a single interaction cannot accommodate.
ποΈ Q: How does Wayfinder prevent the pitfalls of traditional waterfall development?
A: Waterfall methodologies suffer from excessive low-fidelity upfront planning. Wayfinder avoids this by mandating high-fidelity prototypes as a core ticket type, ensuring early feedback and iterative adjustments throughout the planning process.
ποΈ Q: Why are the specifications generated by Wayfinder considered non-persistent?
A: In this workflow, specifications function solely as a destination document to manage complex, multi-session work. Once the project reaches completion and the specifications are integrated into the final codebase, the associated issue tracker documents are deleted rather than maintained as long-term artifacts.
π Book Recommendations
βοΈ Similar
- ποΈ Mythical Man-Month by Frederick Brooks explores the complexities of large-scale software project management and the necessity of thoughtful organization.
- 𧩠Software Engineering at Google by Titus Winters et al. details how to manage massive codebases and complex development lifecycles through standardized engineering practices.
π Contrasting
- π Lean Software Development by Mary Poppendieck and Tom Poppendieck advocates for eliminating waste and minimizing heavy upfront documentation, contrasting with structured spec-driven approaches.
- π Getting Things Done by David Allen provides a personal productivity framework focused on immediate, individual action rather than complex, collaborative, or agent-based orchestration.
π¨ Creatively Related
- π§ Thinking, Fast and Slow by Daniel Kahneman examines the cognitive biases and mental models that influence how humans make decisions under uncertainty, much like navigating the fog of war in software planning.
- πΊοΈ The Art of Strategy by Avinash Dixit and Barry Nalebuff analyzes game theory to help individuals navigate competitive environments and dependent decision-making scenarios.