All authors
Claude Skills by justinjdev
github.com/justinjdev20 skills0 installs28 views
- Openspec Apply ChangeImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.Votes: 0GitHub stars: 5
- Openspec Archive ChangeArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.Votes: 0GitHub stars: 5
- Openspec Bulk Archive ChangeArchive multiple completed changes at once. Use when archiving several parallel changes.Votes: 0GitHub stars: 5
- Openspec Continue ChangeContinue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.Votes: 0GitHub stars: 5
- Openspec ExploreEnter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.Votes: 0GitHub stars: 5
- Openspec Ff ChangeFast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.Votes: 0GitHub stars: 5
- Openspec New ChangeStart a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.Votes: 0GitHub stars: 5
- Openspec OnboardGuided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.Votes: 0GitHub stars: 5
- Openspec Sync SpecsSync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.Votes: 0GitHub stars: 5
- Openspec Verify ChangeVerify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.Votes: 0GitHub stars: 5
- CouncilUse at the start of any non-trivial task. Loads focused, task-relevant context by reading CLAUDE.md, scanning for related files, and producing a structured Session Context block. Invoked automatically by quest or standalone via /council.Votes: 0GitHub stars: 5
- FellowshipMulti-task orchestrator. Coordinates agent teammates (led by Gandalf) running /quest (code) or /scout (research) workflows. Use when you have multiple independent tasks to run in parallel.Votes: 0GitHub stars: 5
- Gather LoreUse BEFORE writing any code in an unfamiliar area. Studies reference files from CLAUDE.md to extract conventions and patterns. Prevents "wrong approach" code review rework by understanding how things are done before writing anything.Votes: 0GitHub stars: 5
- LembasUse between workflow phases or when context feels bloated. Writes a structured checkpoint capturing task, findings, files, state, and next steps, then continues from that summary instead of the full history. Invoke standalone or automatically between quest phases.Votes: 0GitHub stars: 5
- LorebookLoad phase-specific guidance from a quest template. Invoke at the start of each quest phase when a template has been assigned.Votes: 0GitHub stars: 5
- MissiveFetches GitHub issue context for quest spawning. Parses issue references, retrieves structured data via gh, and produces branch suggestions and PR keywords. Used standalone or as input to quest orchestration.Votes: 0GitHub stars: 5
- QuestUse for multi-file or multi-step changes that need research and a plan — not single-file fixes under ~50 lines that follow an existing pattern (see Escape Hatch below). Runs the Research → Plan → Implement → Review lifecycle with a hard gate leaving each of the first three phases and context compaction between them.Votes: 0GitHub stars: 5
- RetroPost-fellowship retrospective analysis. Collects gate history, palantir alerts, and quest metrics to surface patterns and interactively recommend configuration improvements.Votes: 0GitHub stars: 5
- ScoutResearch & analysis workflow. Investigates questions, gathers findings, optionally validates with a fresh subagent. Produces a report — no code, no PRs, no commits. Use standalone or as a fellowship teammate.Votes: 0GitHub stars: 5
- WardenUse AFTER writing code and BEFORE submitting a PR. Simulates a strict code reviewer by comparing changes against reference files and documented conventions. Catches "we don't do it that way" feedback before your human reviewer does.Votes: 0GitHub stars: 5