Loading...
Loading...
Found 127 Skills
Create a living specification (Spec) or plan for a feature by analyzing requirements and codebase
Create detailed, phased implementation plans through interactive research and iteration. Use when the user explicitly asks to "create a plan", "plan the implementation", or "design an approach" for a feature, refactor, or bug fix. Do not use for quick questions or simple tasks.
Creates a comprehensive, context-rich implementation plan through deep codebase analysis, a short clarifying interview, and external research. Accepts a tracker ticket (a Jira/Linear/GitHub key or URL, fetched from the tracker) or a free-form feature request. Use when you have a ticket or feature and need a one-pass-ready plan before writing any code.
Retrieve and explore DeepWiki-generated documentation for public GitHub repositories. Use when listing repository documentation topics, reading DeepWiki pages, or asking focused questions about a codebase that needs current repository structure, architecture notes, or component explanations.
Research a specific system and create or update its blueprints/ documentation
Analyze codebase structure, dependencies, changes, and cross-agent handoffs. Use when user asks about project structure, where code is located, how files connect, what changed, how to resume work, or before starting any coding task.
Comprehensive project architecture blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks and architectural patterns, generates visual diagrams, documents implementation patterns, and provides extensible blueprints for maintaining architectural consistency and guiding new development.
Transform codebases into authentic, interview-defensible resume project experience. Use when analyzing a codebase for: (1) Extracting resume-ready project descriptions, (2) Preparing for technical interview questions about past projects, (3) Understanding the engineering depth and value of a codebase, (4) Identifying defensible technical achievements. Prioritizes correctness and interview credibility over exaggeration.
Resolve implementation ambiguities before planning begins. Two modes: Discussion mode surfaces gray areas with concrete options for greenfield work. Assumptions mode reads the codebase, forms evidence-based opinions, and asks the user to correct only what's wrong (brownfield work). Use for "discuss ambiguities", "resolve gray areas", "clarify before planning", "assumptions mode", "what are the gray areas", "before we plan". Do NOT use for broad design exploration (use feature-design) or for planning itself (use feature-plan).
Hypothesis-driven deep research swarm. Spawns specialist sub-agents to investigate a task across codebase patterns, web sources, MCP tools, installed skills, and project dependencies — with evidence grading and adversarial challenge. Activates on: research, investigate, discover, deep research, how should I, what's the best way, explore options, analyze approaches, scout, prior art, feasibility.
Assess a Rails app's full codebase for compliance with privacy laws, like GDPR and LGPD. Generates an assessment report, not a legal audit.
Process large codebases (>100 files) using the Recursive Language Model pattern. Orchestrates parallel sub-agents to map-reduce across files without context rot. Use when: analyzing large repositories; auditing security or auth across many files; finding patterns across 50+ files; processing large log files or data dumps