Loading...
Loading...
Found 107 Skills
Structured feature brainstorming with diverge/converge methodology. Use when ideating on new features, exploring solutions, or generating creative approaches.
Scrum methodology including sprints, ceremonies, backlog management, and agile practices. Activate for sprint planning, standups, retrospectives, and agile workflows.
Plan document manager -- create, modify, and organize plan.md with Phase/task structure. 기획서(plan.md) 자동 생성/추가/수정 스킬. Triggers: /plan, "create plan", "기획서", "plan 생성", "Phase 추가"
Use before committing to a task. Provides complexity analysis and scope assessment. Invoke when user asks "how complex" or before large features.
Track management methodology - creating and managing logical work units (features, bugs, refactors) through specification, planning, and implementation phases.
Create implementation plans with tasks grouped by subsystem. Related tasks share agent context; groups parallelize across subsystems.
Break down complex tasks into atomic, actionable goals with clear dependencies and success criteria. Use this skill when you need to plan multi-step projects, coordinate agents, or decompose complex user requests into manageable sub-tasks.
Provide development estimates for tasks, features, or projects. Use when user asks for time estimates, effort assessment, or project sizing.
Plan Requirements - generates a structured requirements document, asking clarifying questions about ambiguities before proceeding
Imagine the project already failed, then work backward to find why. More powerful than risk assessment because it assumes failure is certain. Use when user says "pre-mortem", "premortem", "imagine this failed", "what could go wrong", "risk analysis", "before we launch", "stress test", "what would kill this", "project risks".
Break an approved spec into ordered implementation tasks with dependencies, sequencing logic, and done criteria.