fightZy

advanced-brainstorming

Use when a user wants idea generation to become broader, less conservative, more imaginative, or more frame-breaking, especially when expanding an existing proposal into multiple unconventional but still intelligible directions.

closure-retrospective

Extract reusable mechanisms when a non-trivial task is substantively complete and evidence may justify durable guidance in a skill or applicable AGENTS.md / CLAUDE.md, especially after repeated corrections, tool friction, sequencing loops, stable scope boundaries, or decisions that clearly improved results.

Code & Development Listed

dispatching-code-review-subagents

Use when preparing to delegate code review to subagents — after implementation milestones, before merging complex changes, or when the diff spans multiple domains.

idea-credibility-analyst

Use when a user wants to evaluate a product, startup, feature, or workflow idea by clarifying the idea through dialogue, researching similar products and discussions, comparing alternatives, assessing market crowdedness, deep-diving leading competitors and persistent user complaints in crowded spaces, and deciding whether to continue, pivot, or stop.

openspec-discovery

Use when scope is unstable or requirements are unclear, before creating OpenSpec artifacts. Covers codebase investigation, requirement clarification, option comparison, and decision convergence.

openspec-superpower-orchestration

Use when a non-trivial change should follow an OpenSpec-plus-superpower workflow with formal specs, approval gates, implementation discipline, and no parallel planning system

receiving-feedback

Use when receiving feedback, suggestions, criticism, or review on any work — before acting on it. Especially when feedback seems unclear, questionable, conflicts with prior decisions, or asks for "professional" expansion.

workspace-memory-skill

Use when the task involves creating, maintaining, or querying repo-local workspace memory for a project. This skill organizes team-shared agent memory as Markdown files under the current workspace, captures session summaries, maintains layered memory indexes, crystallizes durable team conventions and design rationale, and retrieves memory progressively to reduce context and token cost.

workspace-memory-benchmark-analysis

Use when the user wants to run workspace-memory benchmarks, interpret retrieval results, or map benchmark failures to likely ranking, lineage, or fallback defects before optimizing the system.

Testing & QA Listed

workspace-memory-benchmark-authoring

Use when the user wants to add or expand workspace-memory benchmark fixture coverage, especially for complex retrieval cases that can be drafted safely by subagents under the benchmark fixture directory.