Loading...
Loading...
Found 209 Skills
Strategic planning specialist for task breakdown, dependency management, timeline estimation, and resource allocation. Manual invocation only - expert at decomposing complex projects into manageable tasks, identifying dependencies, assessing risks, and creating actionable roadmaps. Use when starting complex projects, facing overwhelmed scope, needing structured approaches, or requiring systematic task management before implementation.
Universal project planning for non-technical projects. Domains: business, personal, creative, academic, organizational, events. Capabilities: goal setting, milestone planning, resource allocation, timeline creation, risk assessment, progress tracking. Actions: create, plan, structure, breakdown, track projects. Keywords: project plan, roadmap, strategy, goal setting, milestones, timeline, action plan, project management, business plan, personal goals, creative project, academic planning, event planning, organizational change, OKRs, SMART goals, Gantt chart. Use when: creating project plans, setting goals/milestones, planning business initiatives, organizing events, structuring academic work, developing strategies/roadmaps.
View a plan's tasks and progress, regardless of output format.
Team workflow-oriented planning skill (Phase 2). Before development, refine Jira Story + UI mockups into executable plans and output to docs/plans/{Story-Key}/plan.md
Facilitates collaborative design exploration before implementation. Explores user intent, constraints, and requirements through structured dialogue, then produces an approved design document. Must be invoked when entering plan mode or planning any implementation. Triggers: brainstorm, design, plan, "let's think through," "how should we build."
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.
Research codebase, write concrete implementation plan. Use after brainstorming.
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.
Manus-style file planning system for organizing and tracking progress of complex tasks. Creates three files: task_plan.md, findings.md, and progress.md. Use when users request planning, breaking down, or organizing multi-step projects, research tasks, or work requiring more than 5 tool calls. Supports automatic session recovery after /clear. Trigger phrases: task planning, project planning, create plan, break down task, multi-step planning, progress tracking, file planning, help me plan, break down project
Use when starting a new project from scratch, before any technical decisions, to explore the idea through structured sessions and produce a brainstorming synthesis
Interactive project planning for PRD, architecture, and epic/story generation. Use for new projects, planning features, creating PRDs, designing architecture, breaking down work into epics and stories.