superharness

Session start guide: explains how to use superharness skills and conventions. Injected by SessionStart hook.

Superharness brainstorming skill. You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Main entry point: end-to-end workflow for building features. Use /superharness:go 'requirement' to start. Orchestrates brainstorm → plan → TDD implementation → review → QA.

Infrastructure skill: start a local visualization server that renders Mermaid diagrams in the browser. Write .mmd files with pure Mermaid code, the browser updates in real-time via WebSocket (no page reload). Used by brainstorm, writing-plans, and other skills.

Surface unresolved decisions in a development request and ask the user before implementing. Use when starting a non-trivial dev task whose requirements leave open questions that would change the implementation (scope, data shape, UX behavior, compatibility), or when the user asks to confirm first ("先确认一下", "有不清楚的先问").

Discover an existing project's conventions from real evidence and write them as the project spec: AGENTS.md + CLAUDE.md as the thin always-loaded entry, with detail under .superharness/spec/. Use when a project lacks AGENTS.md/CLAUDE.md, when asked to generate conventions ("生成规范", "discover conventions"), or when the spec is stale.

Fix QA issues: reads qa-issues.json written by superharness qa, fixes each issue using TDD, then re-runs QA to verify.

Persist durable learnings from the current session (user corrections, pitfalls and fixes, project decisions not visible in code) into the project knowledge wiki at .superharness/learnings/. Use when the user asks to summarize or persist learnings ("总结一下经验", "沉淀一下", "记住这个"), or when triggered automatically at session end.

Wrapper skill that invokes the superharness qa CLI command from within the AI tool session.

After ALL development on a task is complete, run one terminal review-and-test pass: Spec Review, then Code Review, then the test suite. Use when wrapping up a coding task ("终检", "补测试", "final review", finishing development) — not during development, and not per change.

Scan the project codebase to discover conventions, tech stack, and patterns, then update .superharness/spec/. Primarily invoked by brainstorm as Step 1. Can also be run manually when the user asks to scan or re-scan the codebase for conventions.

Save a user-stated convention or rule to .superharness/spec/. Triggers when the user explicitly says 'save this as a convention', 'from now on use X', 'add to project rules', '记住这个约定', '保存为项目规范', or any instruction to persist a project-level guideline.

Use when executing implementation plans with independent tasks in the current session

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when implementing any feature or bugfix, before writing implementation code

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Session start guide: explains how to use superharness skills and conventions. Injected by SessionStart hook.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when you have a spec or requirements for a multi-step task, before touching code. Creates implementation plans with bite-sized TDD tasks for superharness workflows.