superspecexecute
Use when executing implementation plans in current session. Dispatches fresh subagent per task with two-stage review. Spec Reviewer validates against Specs, Quality Reviewer checks code quality.
浏览 HankLiu447 维护的已发布 AI 技能,比较用途与说明,并通过来源仓库了解安装方式。
已收录技能
21收录技能的仓库 Stars 合计
42仓库 Forks
0平均每个技能的仓库 Stars
2同一仓库中的多个技能可能共享 Stars,合计包含重复仓库数据。
Use when executing implementation plans in current session. Dispatches fresh subagent per task with two-stage review. Spec Reviewer validates against Specs, Quality Reviewer checks code quality.
Use when encountering any bug, test failure, or unexpected behavior. ALWAYS find root cause before attempting fixes. Symptom fixes are failure.
Use at the start of any conversation - establishes how to find and use SuperSpec skills. Combines development discipline with spec-driven documentation.
Use when implementation is complete, all tests pass, and you need to integrate the work. Guides completion by presenting structured options for merge, PR, or cleanup.
Use when implementing any feature or bugfix, before writing implementation code. Each Scenario in Specs becomes a test case following RED → GREEN → REFACTOR cycle.
Use after verification passes to archive completed changes. Applies delta specs to main specs and moves change to archive.
Use when receiving code review feedback, before implementing suggestions. Requires technical rigor and verification, not performative agreement or blind implementation.
Use when you have a written implementation plan to execute in a separate session with review checkpoints. Alternative to subagent-driven development for batch execution.
Use after completing tasks to review code for quality and spec compliance. Two-stage review: Spec Compliance first, then Code Quality.
Use after implementation is complete to verify that code matches specifications. Ensures every Requirement is implemented and every Scenario has a corresponding test.
Fast-track from idea to implementation-ready plan in one session. Combines brainstorm (4 phases) + validate + plan into a single flow. Use for small-to-medium features that don't need separate review points.
Use after specs are validated to create TDD implementation plan. Each Scenario in Specs becomes a test case in the plan. Combines bite-sized TDD tasks with spec references.
Execute Gemini CLI for AI-powered code analysis and generation. Use when you need to leverage Google's Gemini models for complex reasoning tasks.
Use before any feature work. Progressive design flow with four phases: Explore → Propose → Design → Spec Outputs: proposal.md, design.md, specs/*.md
Execute Codex CLI for code analysis, refactoring, and automated code changes. Use when you need to delegate complex code tasks to Codex AI with file references (@syntax) and structured output.
Phase execution protocol to prevent context drift during long development sessions. MUST be read at the start of each phase and referenced in the last TODO of each phase. This ensures AI maintains context acros...
External AI code review using Codex or Gemini. Reads project.yaml to determine which provider to use for frontend vs backend tasks. Includes hallucination detection to avoid blindly applying AI suggestions.
Use to validate spec documents for correctness, completeness, and consistency. Ensures specs follow SuperSpec format and are ready for implementation.
Use when about to claim work is complete, fixed, or passing. REQUIRES running verification commands and confirming output before making any success claims. Evidence before assertions, always.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies. Dispatch one agent per independent problem domain for parallel execution.
Use when starting feature work that needs isolation from current workspace. Creates isolated git worktrees with smart directory selection and safety verification.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。