Create comprehensive technical design documents in Chinese for software projects. Use when the user requests technical architecture design, system planning, or needs a detailed technical specification document (技术方案设计.md). Focus on gathering requirements, analyzing context, and producing structured design documents with architecture diagrams, component specifications, and implementation plans.
Guide users through structured dialogue to transform vague ideas into clear, actionable product concepts. Uses one-question-at-a-time approach with multiple choice options. Use this skill when: - User says "I have an idea", "I want to build", "let me think about" - User mentions "brainstorm", "explore ideas", "think through" - Requirements are vague, incomplete, or user seems unsure what they want - Need to explore problem space before jumping to solutions - Running /pm.plan but requirements are unclear or missing context - User asks "what should I build?", "how should this work?" Process: Ask ONE question at a time, prefer multiple choice, explore 2-3 approaches before settling.
Automatically bridge long technical sessions to keep context window small and costs low. Extracts key technical decisions, resolved bugs, active tasks, and essential code snippets from conversation history into a compact markdown summary (2,000–5,000 tokens). Use when reaching a project phase milestone, when Claude warns the context window is getting full, or to start a fresh session with minimal token cost while maintaining continuity.
Reviews and categorizes GitHub issues by difficulty (easy/medium/hard). Use when you need to triage open issues, ask clarifying questions for incomplete issues, or write implementation plans for ready issues.
LLM-only skill that analyzes a snapshot of a single disk or partition and generates a safe, structured cleanup plan. Identifies obvious junk, heavy folders, and proposes step-by-step actions to reclaim space without risking important data.
Create comprehensive implementation plans for engineers with minimal codebase knowledge. This skill should be used when breaking down features into detailed, step-by-step implementation guides following TDD principles.
Triage a production incident with safe, minimal changes and rollback guidance.
Answer Linear issues tagged with "question". Explores codebase and produces decisions - never code changes or PRs. Triggers - answer questions, linear questions, question triage.
Create structured use case documentation with sequence diagrams for backend systems. Use when documenting API endpoints, service interactions, event flows, or system behaviors. Triggers on requests like "document this use case", "create use case for X endpoint", "write flow documentation", or "explain how X feature works".
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
Identify and resolve ambiguities in specifications through structured questioning. Use when specification has [NEEDS CLARIFICATION] markers, when user mentions unclear or ambiguous requirements, before creating implementation plans, or when planning reveals specification gaps.
Processes BlackBelt coaching call transcripts and generates Basecamp-ready summaries. Can post directly to Basecamp. Use when "process meeting transcripts", "summarize BlackBelt meetings", "check for new transcripts", "post to basecamp".
Acts as an intellectual sparring partner to critique, challenge, and refine thinking through Socratic questioning and alternative perspectives. Activates automatically when detecting complex decision-making, strategic planning, or multi-consideration problems where critical evaluation adds value. Also activates when user explicitly asks to "challenge my thinking", "critique this idea", "what am I missing", "play devil's advocate", or similar requests for critical analysis. Includes synthesis mode to integrate feedback into refined positions.
This skill should be used for interactive clarification with smart HIL question flows. Triggers include "ask me questions", "help me think through", "what should we consider", session start ("what are we working on"), scope definition ("what's in/out"), or review checkpoints ("does this look right"). Auto-detects context and adapts question depth. Override with explicit mode (ask-deep start, ask-deep scope, ask-deep review).
This skill should be used when the user asks to "clarify requirements", "refine the PRD", "ask clarifying questions", "fill in PRD gaps", "run a clarification session", or after generating a PRD that needs refinement. Uses structured questioning through AskUserQuestion tool to transform ambiguous requirements into actionable specifications.
Navigate CA Lobby documentation structure quickly. Use when searching for CA Lobby docs, finding phase reports, locating master plan, or user says "find documentation". Provides instant access to project documentation.
This skill should be used when the user asks about "MADR format", "MADR template", "Markdown Architectural Decision Records", "MADR 4.0", "MADR sections", or needs guidance on creating ADRs using the MADR (Markdown Architectural Decision Records) format.
This skill should be used after productive sessions to extract learnings and route them to appropriate Reusable Intelligence Infrastructure (RII) components. Use when corrections were made, format drift was fixed, new patterns emerged, or the user explicitly asks to "harvest learnings" or "capture session intelligence". Transforms one-time fixes into permanent organizational knowledge by implementing updates across multiple files.
This skill should be used when the user asks to "design a feature", "make architectural decision", "choose a pattern", "select technology", "plan structure", "decide on approach", or requests technical design before implementation. Use for architectural planning, pattern selection, and technical decision-making. Do NOT use for direct code implementation, bug fixes, or simple edits.
Apply critic feedback to improve an engineering spec. Use when revising a spec based on review comments to address issues and improve quality scores.
Analyze implementation failures and generate recovery plans. Use when an issue fails and needs diagnosis for retry or escalation.
Best practices for implementing features. Use when building pages, wiring API integrations, or assembling organisms.
This skill should be used after productive sessions to extract learnings and route them to appropriate Reusable Intelligence Infrastructure (RII) components. Use when corrections were made, format drift was fixed, new patterns emerged, or the user explicitly asks to "harvest learnings" or "capture session intelligence". Transforms one-time fixes into permanent organizational knowledge by implementing updates across multiple files.
Activates the "Distinguished Principal Full Stack Engineer" persona. Use this skill when the user requests "ULTRATHINK", demands high-level architectural analysis, or specifically asks for expert, "zero-fluff" engineering advice. This skill governs behavior, tone, and output format for complex full-stack and architectural tasks.
