All authors
Claude Skills by rjroy
github.com/rjroy27 skills2 installs85 views
- Add ItemThis skill should be used when the user asks to "create an issue", "add an item", "add a bug", "create a task", "add to backlog", or invokes /compass-rose:add-item. Creates a new repository issue and adds it to the project with custom fields.Votes: 0GitHub stars: 6
- BacklogThis skill should be used when the user asks to "review backlog", "analyze backlog quality", "backlog health", "recommend items", or invokes /compass-rose:backlog. Reviews backlog items and analyzes quality to recommend best items to work on.Votes: 0GitHub stars: 6
- Next ItemThis skill should be used when the user asks "what should I work on", "next item", "highest priority", "what's ready", or invokes /compass-rose:next-item. Recommends the highest-priority ready item with rationale.Votes: 0GitHub stars: 6
- ReprioritizeThis skill should be used when the user asks to "reprioritize", "update priorities", "scan codebase for relevance", or invokes /compass-rose:reprioritize. Provides codebase-aware priority recommendations with batch update capability.Votes: 0GitHub stars: 6
- BrainstormUse 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.Votes: 0GitHub stars: 6
- Define ValidationUse 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".Votes: 0GitHub stars: 6
- DesignUse 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".Votes: 0GitHub stars: 6
- ImplementUse when ready to build from the user's current request or intent, optionally informed by a spec, design, plan, or notes. Triggers include "implement this", "build this", "implement the request/intent", "continue implementation", and "resume where we left off".Votes: 0GitHub stars: 6
- Poke HolesThis skill shifts posture to adversarial/rigorous mode for challenging ideas. Appropriate when the user wants critical analysis, not validation. Triggers include "poke holes in this", "tear this apart", "what am I missing", "stress test this", "find what's wrong", "challenge this", "play devil's advocate", "what could go wrong".Votes: 0GitHub stars: 6
- Prep PlanUse to think through an implementation approach with the user, discuss useful evidence, and optionally record a working plan. Input can be conversational intent, design, brainstorm, research, or a prompt. Triggers include "prep plan", "prepare a plan", "plan this", "make a plan", "plan the implementation", and "break this into steps".Votes: 0GitHub stars: 6
- ResearchUse 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".Votes: 0GitHub stars: 6
- RetroUse 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".Votes: 0GitHub stars: 6
- InitInitialize mind-reader plugin - creates directories, generates baseline script, runs initial computationVotes: 0GitHub stars: 6
- IssuesThe lore directory redesign names an extraction skill that surfaces mistakes from build artifacts (especially retro notes) at design time, with a human gate, and promotes confirmed mistakes into `.lore/learned/`. The shape is sketched in the redesign brainstorm but not designed.Votes: 0GitHub stars: 6
- IngestUse when distilling useful project understanding from eligible .lore/ artifacts into the reference wiki. Historical artifacts suggest candidates; current claims are checked against implementation and tests. Triggers include "ingest this", "distill reference knowledge", "update the reference", and "populate the field guide".Votes: 0GitHub stars: 6
- LintThis 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'.Votes: 0GitHub stars: 6
- QueryUse 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.Votes: 0GitHub stars: 6
- SimplifyUse when the user wants to simplify or clean up code without changing behavior. Accepts standalone scope or user-selected findings from /refactor.Votes: 0GitHub stars: 6
- VisionThis 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".Votes: 0GitHub stars: 6
- InitUse 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".Votes: 0GitHub stars: 6
- Resolve DriftUse 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".Votes: 0GitHub stars: 6
- StratifyUse when the wiki has outgrown its flat layout and pages need grouping into category directories. Reorganizes .lore/reference/ into category and subcategory trees, rewrites the index, and repairs every referrer. Triggers include "stratify the wiki", "organize the reference directory", "group the wiki into categories", "the wiki is too flat", and "reorganize the field guide".Votes: 0GitHub stars: 6
- Update EvidenceUse 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".Votes: 0GitHub stars: 6
- Install FormulaInstall the reusable lore-development Beads formula into the current project. Use when a project should run the lore-development workflow through bd molecules.Votes: 0GitHub stars: 6
- IntentUse when the user wants to think through what to build and why. Produces a conversational record of intent and context, not a requirements contract. Triggers include "help me shape this idea", "what should we build", or "capture the intent".Votes: 0GitHub stars: 6
- MigratePreview and, after explicit user confirmation, migrate pre-work and .lore/work lore layouts into historical intents, shared work, and gitignored local paths, converting legacy HTML artifacts to Markdown with original-byte backups. Does not migrate project files automatically.Votes: 0GitHub stars: 6
- RefactorUse to inspect a bounded area for code smells and discuss whether a behavior-preserving cleanup is worthwhile. Diagnosis only; implementation happens separately through simplify when the user asks to proceed.Votes: 0GitHub stars: 6