plan
Review memory bank state and create/update an implementation plan
Discover tools knowledge base skills, compare source repositories and read the instructions for each workflow.
Review memory bank state and create/update an implementation plan
Systematically gather source material for blog articles. GitHub history, session transcripts, code examples, screenshots. Use at RESEARCH stage of blog pipeline.
Multi-persona documentation review that catches quality failures AND signal mismatches. Produces prioritized edits, not assessment. Quality before signals.
Fact-check and verify technical accuracy of blog articles. Code examples, links, claims, dates. Use at TECHNICAL stage of blog pipeline.
Identifies missed training sessions and proposes plan reshuffles with motivational support. Use for weekly check-ins, when multiple sessions are skipped, or when user asks for help getting back on track.
Create D3 questions focused on written explanations and reflections of static content (text, images, diagrams). For video-based questions, use implement-video-question instead.
Self-healing documentation lookup. Use when wondering how something in the Awareness project works, where files live, or how to do something technical. Queries tech RAG and spawns improvement agents for gaps.
Generate 1-page pursuit briefs for qualified RFP opportunities. Use when creating bid/no-bid decision documents or implementing pursuit brief generation features.
Fetches bug tickets from Jira using Atlassian MCP and formats them for AI-assisted bug fixing. Use when user mentions a Jira ticket key (like EMS-1234, PROJ-567) and wants to fix a bug, or when starting a bug-f...
Expert guidance for managing tasks using the Backlog.md CLI tool. Use this skill when working with backlog tasks, creating or editing task files, managing acceptance criteria, tracking task progress, or underst...
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
Record decisions to docs/decisions.md. Run manually after finishing features with interesting trade-offs, when making architectural choices worth remembering, or when confusion about past decisions signals one...
Maintain skills wiki health - check links, naming, cross-references, and coverage
Dispatch to the right problem-solving technique based on how you're stuck
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or to...
Skills wiki intro - mandatory workflows, search tool, brainstorming triggers
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow help...
Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
Query the knowledge graph for learnings, patterns, and mistakes. Use when you need to find past learnings, avoid known mistakes, discover established patterns, or search for relevant knowledge before implementi...
Manage session lifecycle, learning extraction, and context metrics. Use when starting/ending sessions, analyzing workflows for learnings, querying knowledge graph, or checking session metrics.
Index and search project documentation with semantic similarity. Use when you need to find relevant documentation, check if docs are indexed, or link documentation to code entities.
Session startup - reads recent session logs, produces overview, suggests next steps. Pairs with /bye. Use at the start of a session or when returning after a break.
Use Codex CLI for web search, code review, and writing review. Triggers on (1) web search requests, (2) code review of git changes, (3) writing/file review. Use for "search the web for...", "review this code",...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.