vibe-garden

Use when checking whether field-guide reference pages still match current code and tests. Reads pages plus fg-evidence anchors, reports or fixes semantic drift, and can use sub-agents for parallel audit batches. Triggers include "resolve drift", "semantic drift", "check accuracy", "verify the reference against code", and "audit the wiki".

Use after ingesting or editing field-guide pages to attach living code/test anchors. Adds or refreshes fg-evidence metadata without trying to prove prose accuracy. Triggers include "update evidence", "wire evidence", "add evidence anchors", and "connect the wiki to code".

Use when extracting knowledge from .lore/ artifacts into the reference wiki. Converts work artifacts (retros, specs, plans, research, notes) into structured wiki pages grouped by knowledge type. Reads Markdown or HTML sources and writes Markdown by default. Triggers include "ingest this", "extract knowledge from", "add this to the wiki", "update the reference from", and "populate the field guide".

Use when setting up field-guide on a project for the first time, or to refresh the scheduled lint job after it expires. Triggers include "init field-guide", "set up field-guide", "refresh field-guide lint schedule", and "bootstrap the wiki".

This skill is used when the project wiki needs a health check. Triggers include 'lint the wiki', 'check wiki health', 'run field-guide lint', 'are there stale wiki pages', 'find orphaned pages', 'check for contradictions in the wiki'.

Use when asking questions about the project wiki, querying accumulated knowledge, searching project decisions or lessons. Triggers include "query the wiki", "what does the wiki say about", "search project knowledge", and natural language questions directed at the field-guide wiki.

Use when exploring before committing, thinking through trade-offs, or digesting sketches and diagrams. Triggers include "let's brainstorm", "what if we...", and "explore options". Bad ideas welcome, questions over answers, mistakes on purpose.

Use to add validation criteria to a spec or plan. Triggers include "define validation", "how will we validate", "what should the AI check", and "add validation to this".

Use when the user has a specific architecture, tool, or technique in mind and wants to explore whether and how it applies. Not full-feature design but a focused technical investigation of one element. Triggers include "design this", "I want to use X for this", "how should this work technically", and "explore this approach".

Use when ready to build from a spec, design, or plan, or to resume from notes. Triggers include "implement this", "build this", "implement the spec/design/plan", "continue implementation", and "resume where we left off".

Use when a plan exists and needs validation gates added to each step before implementation begins. Produces task files that implement can consume. Triggers include "break down this plan", "add validation to the plan steps", "plan-breakdown", and "gate this plan".

Use when ready to build a reviewable implementation plan as a lore artifact. Input can be a spec, design, brainstorm, research, or a well-defined prompt. Triggers include "prep plan", "prepare a plan", "plan this", "make a plan", "plan the implementation", and "break this into steps".

Use when specifics matter more than general training knowledge, or when details are newer than the training cutoff. Triggers include "research this", "find documentation for", "look up how X works", "what's the current state of", and "what's the prior art".

Use when completed work needs to be recorded as a lore artifact covering what happened, what surprised, what broke, and what drifted. Observation only, not interpretation. Triggers include "let's do a retro", "/retro", "review what happened", "capture what happened", and "write up the session".

This skill should be used when the user wants to clean up code without changing behavior. Dispatches cleanup agents, runs tests to verify behavior is preserved, then runs code review. Triggers include "simplify this", "clean up this code", "refactor without changing behavior", "reduce complexity".

This skill should be used when the user wants to define the requirements of a feature or project. Produces numbered requirements and validation criteria. Triggers include "write a spec for", "define the requirements", "what should this do", "capture the requirements".

This skill should be used when the user wants to define the north star for a project — why it exists, what problems it solves, what it would never become. Suited for the start of a project or when direction feels unclear. Triggers include "define the project vision", "what should this project become", "create a vision document", "what are we building toward".

Use when the user says "file an issue", "log this", "track this", "add a bug", "create a task", "add to backlog", or invokes /compass-rose:add-item. Replaces /lore-development:file-issue. Creates a local issue file in .lore/work/issues/.

Use when the user asks to "review backlog", "analyze backlog quality", "backlog health", or invokes /compass-rose:backlog. Reads all open and wontfix issue files and analyzes quality via the backlog-analyzer agent.

Use when the user asks "what should I work on", "what's next", "highest priority", "next item", or invokes /compass-rose:next-item. Reads local issue files and recommends the highest-priority open item.

Use when the user asks to "reprioritize", "update priorities", "scan codebase for relevance", or invokes /compass-rose:reprioritize. Scans codebase against local issue files and updates their priority/status meta tags.

Use when a spec, plan, design, or idea needs adversarial review to find what's wrong rather than what's right. Triggers include "poke holes in this", "tear this apart", "what am I missing", "stress test this", "find what's wrong", "challenge this", and "what could go wrong".