Loading...
Loading...
Found 143 Skills
Use for planning work
GainForest beads (`bd`) planning workflow. Activates on ALL user work requests — task planning, epic management, claiming work, closing tasks with commit links, handling blockers. Use before writing any code.
Use when planning home improvement, renovation, or DIY projects that need materials lists, tool requirements, timelines, or seasonal weather considerations
Plan and track projects with timelines, resources, and risk management
Create PLAN.md file with phase-based breakdown for issues. Use after creating an issue with /issue to break down work into phases.
Synthesizes research findings into design decisions via codebase investigation. Use when (1) translating research into implementation approaches, (2) selecting between design alternatives, (3) executing after /research or deep-research, or (4) preparing input for /plan phase.
Use when an agent needs to write user stories for a project
Use when planning with fixed deadline or target outcome, working backward from future goal to present, defining milestones and dependencies, mapping critical path, identifying what must happen when, planning product launches with hard dates, multi-year strategic roadmaps, event planning, transformation initiatives, or when user mentions "backcast", "work backward from", "reverse planning", "we need to launch by", "target date is", or "what needs to happen to reach".
REQUIRED skill for planning and designing coding tasks before implementation. Use this skill when: (1) User asks to "plan", "design", "create a plan", or "think before coding" (2) Complex tasks requiring multiple files or steps (3) Tasks involving both backend and frontend changes (4) Breaking down ambiguous requirements into concrete tasks This skill ensures plans are properly documented, saved as markdown, reviewed by subagent, and registered as todos before any code is written. Do NOT skip this skill for non-trivial tasks.
Plan work before coding: do repo research, analyze options/risks, and ask clarifying questions before proposing an implementation plan. Use when the user asks for a plan, design/approach, scope breakdown, or implementation steps.
Epic orchestration - PM + Tech Lead for planning and formatted execution.
Plan document manager -- create, modify, and organize plan.md with Phase/task structure. 기획서(plan.md) 자동 생성/추가/수정 스킬. Triggers: /plan, "create plan", "기획서", "plan 생성", "Phase 추가"