Guide for creating effective, reusable skills that extend agent capabilities with specialized knowledge and workflows. Use when creating a new skill from scratch, updating an existing skill, designing skill architecture, or when a user says "make a skill for X." Also use when formalizing a workflow, capturing domain…
Systematic process for maintaining skill health through accuracy checks, completeness reviews, and terminology updates. Use when skill names become unclear, terminology needs updating, periodic audits are due, new skills need cross-reference validation, or skills are reported as confusing or outdated.
A skill for general-purpose planning grounded in uploaded files. Creates deeply informed plans from specs, docs, code, research, or images. Includes intent-based routing to select the right planning mode automatically.
Transform specifications into structured, self-contained prompts for autonomous implementation agents. A prompt is a commission — a formal request for craftsmanship.
A structured process for splitting large development tasks into 2-4 independent parallel tracks that can be executed simultaneously, reducing timelines by 50-70% while improving focus and architectural discipline.
A checklist to ensure a smooth and successful handoff of a specification to an autonomous implementation agent. Use before committing a final specification.
Write production-ready, A+ quality specifications for software releases. A spec is a contract, not a wishlist. Encodes the disciplined engineering practice of creating comprehensive, precise, actionable, and testable release specifications.
Formalize the meta-process of strategic scouting as an iterative loop: scout, gather feedback, reframe, re-scout. Use when the initial framing of a problem feels too narrow, after an initial strategic scout has been completed, or when facing a complex strategic decision where the first answer is unlikely to be the…
Guide the design of a coherent multi-surface product strategy where each surface has a unique, complementary role. Use when planning a product across multiple surfaces (desktop, mobile, web, API, CLI), when adding a new surface to an existing product, or when a multi-surface product feels fragmented. Produces a…
Guide the process of reframing a binary product decision into a strategic positioning opportunity. Use when facing keep-or-deprecate, build-or-buy, native-or-web decisions. Identifies the unique value of each option through the unlocking question "What is this uniquely good at?" and produces a positioning statement…
A structured process for exploring strategic tensions, scouting multiple routes, and aligning on a clear vision before committing to a plan. Use when facing a significant strategic decision, when a project feels stuck, when there are competing priorities, or at the beginning of a new project or major release. Produces…
Systematic process for auditing project documentation to detect and correct drift -- the gap between what docs say and what the code actually does. Cross-references every document against the actual codebase to classify findings as Accurate, Drifted, Missing, or Orphaned. Use when documentation feels stale, after…
Conduct a comprehensive 4-phase health audit on any software repository. Evaluates 5 dimensions (critical issues, security, testing, technical debt, documentation) with GREEN/YELLOW/RED classification, generates actionable engineering tasks with file paths and effort estimates, and produces a permanent dated audit…
Map any software system's capabilities using action-verb clusters -- grouping components by what they DO rather than where they LIVE. Produces a behavioral architecture map that reveals capabilities, gaps, cross-cutting concerns, and architectural confusion that directory trees hide. Use this skill whenever you need…
Write and maintain STATUS.md files that provide at-a-glance visibility into project health, progress, risks, and next milestones. Integrates behavioral architecture summaries from semantic clusters and health dashboard data from health audits into a single, honest status document. Use when starting a new project, at…
Six-step ritual for distilling long conversations and sessions into potent wisdom artifacts. Use when compressing a transcript, ending a long session, performing context hygiene, handing off a project, or when the context feels heavy and noisy. Also use when someone asks how to compress, distill, or summarize a…
Three-tier memory hierarchy for cultivating institutional knowledge with growth semantics. Use when writing daily notes, compressing sessions into wisdom, tending the memory garden, promoting artifacts between tiers, or applying the 3-month rule to triage what matters. Also use when someone asks about memory…
Extract and document reusable patterns (seeds) from experiences. Use when reflecting on learnings, capturing a pattern you noticed, documenting a mistake that taught something, or formalizing an insight into a structured artifact. Also use when someone asks how to write a seed, what makes a good seed, or how to…
Manage and apply the 10 Dojo Seed Patches as reusable thinking modules. Use when architecting systems, making design decisions, debugging complex issues, optimizing costs, or when someone asks "what seed applies here?" or "which pattern should I use?" Also use when keywords match seed triggers: governance…