Loading...
Loading...
Found 141 Skills
Structural review of documents for gaps, clarity, completeness, and organization. Use when a brainstorm, plan, spec, ADR, or any doc needs polish before the next workflow step. For exploring new ideas from scratch, use brainstorming instead.
Generate 10 brilliant ideas for powerful new functionality. Use when brainstorming features, improvements, or innovations for a system. Internally generates 100 candidates and filters to the top 10 most impactful, pragmatic, and innovative ideas.
Unified team skill for brainstorming team. All roles invoke this skill with --role arg for role-specific execution. Triggers on "team brainstorm".
Guide for facilitating creative brainstorming sessions using AI, leveraging techniques like SCAMPER, Design Thinking, and lateral thinking.
Use when creating or iterating on a detailed per-subsystem technical design specification from a system spec, before starting OpenSpec workflow. Triggers: "design spec", "subsystem spec", "write the spec for S1", "phase breakdown", "implementation phases", "mid-level spec", "technical design". Encodes opinionated progressive phase discipline with FP progression and contract boundaries. Do NOT use for high-level system specs (use brainstorming) or for OpenSpec artifacts (use openspec directly).
Software architecture and UI/UX principles for building genuinely new solutions, not derivative work. Use when designing features, architecting software, brainstorming apps, reviewing designs, or during strategy discussions. Focuses on first-principles thinking, simplicity where it matters, and creating rather than commenting.
Comet Preset Path: Bug fix / Hotfix. Skip brainstorming, go directly through open → build → verify → archive. Applicable for behavior fixes and scenarios that do not involve new capability design.
Decompose the unified docs/specs/ artifact into parallelizable tasks — the ## Decomposition section of the same document whose ## Design & Rationale section holds the DR-N source. Triggers: 'plan implementation', 'create tasks from spec', or /plan. Applies the verification ladder: verification depth matches each task's blast radius — static analysis for low-risk tasks, scoped tests plus a kill-probe for medium, the integration suite on top for high-risk surfaces (judged test-after, not test-first ordering). Auto-chained from /ideate, or run directly to author the whole unified spec at thin/standard depth. Do NOT use for brainstorming, debugging, or code review.
Interactive brainstorming session, then optionally create a Project or capture knowledge
Design exploration with parallel agents. Use when brainstorming ideas, exploring solutions, or comparing alternatives.
Orchestrates multi-advisor council debates on high-impact architecture, technology, or product decisions. Dispatches 3-5 domain archetype subagents (pragmatic-engineer, architect-advisor, security-advocate, product-mind, devils-advocate, the-thinker) through opening statements, tensions, position evolution, and synthesis phases. Preserves dissent and delivers actionable recommendations with captured risks. Use when evaluating trade-offs, stress-testing a PRD or tech spec, resolving dilemmas with multiple viable options, or when a decision needs diverse expert perspectives. Don't use for simple yes/no questions, factual lookups, creative brainstorming without tradeoffs, or tasks where a single expert perspective suffices.
Stepwise scaffolding, brainstorming, and draft-generation for literary novels using interactive interviews. TRIGGERS - Use this skill when user says: - "create a novel project" / "start a new novel" - "help me brainstorm my novel" / "plan my story" - "/novel-architect [language] novel named [name] [core idea]" - "set up novel structure" / "initialize my book project" - Any request about creating fiction writing projects or story planning Creates full novel directory with foundation files, character sheets, and chapter scaffolding. Uses gentle, reflective interview process to discover emotional truth before structure.