Loading...
Loading...
Found 128 Skills
Prospective failure analysis using Gary Klein's swing-mortem technique. Assumes complete failure, works backward to identify risks, leading indicators, and circuit breakers. Counters optimism bias by forcing systematic exploration of failure modes before they materialize. Use for project plans, architecture decisions, technology adoption, business strategy, or feature launches. Triggers on "리스크", "위험", "실패하면", "swing-mortem", "뭐가 잘못될 수 있어", "risk", "what could go wrong", "걱정되는 점", "failure modes", "리스크 분석", "위험 분석".
Define a new task with structured requirements before implementation. Use when the user says "define task", "new task", "spec this", or wants to formalize a feature/bug/refactor before planning.
Decomposes vague, high-level project requirements into well-scoped planning units for /deep-plan. Use when starting a new project that needs to be broken into manageable pieces.
Check project progress, show context, and route to next action (execute or plan). Triggers include "progress".
Collaboratively turn ambiguous ideas into implementation-ready designs before coding. Use when requests involve new features, behavior changes, architecture decisions, or prompts like "brainstorm", "design this", "plan this", or "think through options". Clarify intent via one-question-at-a-time dialogue, compare 2-3 approaches with trade-offs, and converge on a validated design spec.
Invoke MassGen's multi-agent system for general-purpose tasks, evaluation, planning, or spec writing. Use whenever you want multiple AI agents to tackle a problem, need outside perspective on your work, a thoroughly refined plan, or a well-specified set of requirements. Perfect for: writing, code generation, research, design, analysis, pre-PR review, complex project planning, feature specification, architecture decisions, or any task where multi-agent iteration produces better results than working alone.
Create comprehensive technical roadmaps aligned with business goals. Plan technology investments, architecture evolution, and infrastructure improvements over quarters and years.
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
Structured Autonomy Planning Prompt
Use this skill BEFORE implementing any new feature. This is NON-NEGOTIABLE for scope control. Use when evaluating features during brainstorming, planning new functionality, branches approach size limits (1000/1500/2000 lines, 15/25/30 commits). Do not use when feature is already approved and in progress. DO NOT use when: simple bug fixes with clear scope.
Use when starting a new project from scratch, before any technical decisions, to explore the idea through structured sessions and produce a brainstorming synthesis
View Linear roadmaps. Use when viewing roadmap planning.