git-for-strategy

Split large tasks into independent parallel tracks to maximize velocity. Use when coordinating multiple parallel development streams or organizing dependent tracks. Trigger phrases: 'split into parallel tracks', 'organize these tracks', 'phased parallelism', 'coordinate parallel development', 'define track dependencies'.

Create actionable plans deeply grounded in uploaded files. Use when creating plans from specs, docs, code, or research. Trigger phrases: 'create a plan from this spec', 'analyze these files', 'plan the refactoring', 'what's next from these docs', 'extract action items'.

Write production-ready frontend specifications deeply grounded in existing backend architecture to prevent integration issues. Use when building frontend features on a working backend or redesigning UI for an existing API. Trigger phrases: 'spec the frontend', 'write frontend spec from backend', 'ground the UI in this API', 'integrate this frontend', 'frontend implementation guide'.

Route file-based planning tasks intelligently to specialized modes. Use when creating plans from uploaded specs, docs, code, or research. Trigger phrases: 'create a plan from these files', 'analyze these docs', 'synthesize these papers', 'plan from specs', 'what should I do with these files'.

Write production-ready, A+ quality specifications for software releases. Use when designing new features, systems, or architectures. Encodes the pattern used in Dojo Genesis v0.0.17-v0.0.23 specifications. Trigger phrases include 'write a spec', 'create a specification', 'spec this feature', 'design this system', 'write a release spec'.

Hand off work between agents cleanly, preserving all context and enabling autonomy. Use when one agent completes work and another must begin. Trigger phrases: 'prepare this for handoff', 'hand off to the implementation agent', 'is this handoff package complete', 'ensure nothing is lost in the transition'.

Transform specifications into structured implementation prompts for autonomous execution. Use when preparing to commission agents or converting specs into execution-ready prompts. Trigger phrases: 'write implementation prompt', 'commission this spec', 'convert spec to prompt', 'prepare for implementation', 'create the execution plan'.

Verify specifications are ready before commissioning implementation agents. Use as a quality gate before handoff, to catch spec-to-codebase drift, or before parallel track execution. Trigger phrases: 'verify the spec', 'pre-commission check', 'track 0 alignment', 'ready to commission', 'verify spec-to-code'.

Iterate through scouting cycles by gathering feedback, identifying reframes, and re-scouting with new lenses. Use when initial scouting raises deeper questions. Trigger phrases: 'scout this, gather feedback, then re-scout', 'what is the reframe hiding in this feedback', 'iterate the scout', 'two-scout rule'

Reframe binary product decisions by discovering what a product is uniquely good at. Use when stuck between keep/kill choices. Trigger phrases: 'reframe this binary decision', 'what is this uniquely good at', 'find the complement not the competition', 'is this really a binary choice', 'unlock the positioning opportunity'.

Explore a new project's philosophy and patterns before committing to collaboration. Assess architecture fit, map resonances, and identify entry points. Use when encountering a new codebase, repository, or project. Trigger phrases include 'explore this project', 'assess this codebase', 'should we collaborate on this', 'onboard me to this repo', 'evaluate this project for fit'.

Conduct deep and wide research using structured approaches for investigating topics and synthesizing findings. Use when making informed decisions, exploring problem spaces, evaluating complex systems, or planning features. Trigger phrases: 'research this topic deeply', 'do a wide scan of the landscape', 'explore the competitive space', 'investigate and synthesize', 'understand before deciding'.

Explore strategic tensions and scout multiple routes to find the best path forward. Use when facing a strategic decision with no clear answer. Trigger phrases: 'scout this tension', 'explore multiple routes', 'hold this question open before deciding', 'what are our options here', 'scout to spec pipeline'.

Distill long conversation histories into potent memory artifacts using semantic compression. Use at end of sessions to preserve wisdom while reducing context load. Trigger phrases: "compress this context", "distill this conversation", "create a memory artifact", "condense this history", "extract key wisdom".

Write structured memory entries following the 4-Tier Context Iceberg for efficient context management. Use when recording daily learnings, documenting decisions, or extracting seeds. Trigger phrases: "write a memory entry", "record this learning", "save this to memory", "create a context artifact", "document this insight".

Conduct structured post-sprint retrospectives for continuous improvement and learning harvest. Use after major releases, significant milestones, or when projects feel stuck. Trigger phrases: 'do a retrospective', 'what did we learn', 'reflect on this release', 'harvest the learnings', 'what went well and what was hard'.

Extract and document reusable patterns from experiences using evidence-based frameworks. Use after projects or when patterns emerge across contexts. Trigger phrases: "extract the learnings", "document this pattern", "turn this into a seed", "what can we learn from this", "capture this insight".

Access and apply the 10 Dojo Seed Patches plus 3 field seeds as reusable thinking modules. Use when architecting systems, optimizing costs, debugging complex issues, or grounding ecosystem-level work. Trigger phrases include "which seed applies here", "suggest a seed pattern", "apply a seed to this", "what pattern should we use", "load the seed library".

Generate comprehensive living status documents for software repositories combining filesystem exploration, semantic clustering, file importance ranking, and health assessment. Use when understanding codebases, auditing repos, creating system maps, assessing health, or onboarding to projects. Trigger phrases: 'give me a complete repo overview', 'understand this codebase', 'what does this repo do', 'create a system map', 'audit this repository', 'build a mental model'.

Write comprehensive status documents for software projects using a 10-section template bridging heartbeat, anatomy, and checkup perspectives. Use when writing status reports, creating project overviews, documenting codebase state, preparing handoffs, or auditing project health. Trigger phrases: 'write a status report', 'give me the lay of the land', 'where are we right now', 'create a project overview', 'document the current state', 'prepare a handoff document'.

Write and update STATUS.md files to provide at-a-glance visibility into project health as a single source of truth. Use at project start, during weekly syncs, after major releases, or whenever project status significantly changes. Trigger phrases: 'create a status file', 'update the project status', 'what's the current state', 'document where we are', 'create a status dashboard'.