📌Project Management Skills
Browse skills in the Project Management category.
Jira
A powerful skill for Claude agents.
Avoid Feature Creep
A powerful skill for Claude agents.
create-progress-pr
Create a traceable progress planning file under docs/progress/ from PROGRESS_TEMPLATE.md, capturing goals/acceptance criteria/scope/I-O contract/decisions/risks/step checklist, then open a GitHub PR with gh (no feature implementation yet). Use when the user and agent have aligned on a new feature and want an executable plan to guide future work and review.
worklog
Update the WORKLOG.md with session progress, architectural decisions, lessons learned, and next steps
battle-plan
Creates a comprehensive action plan that addresses both substance (strengthening your proposal, filling evidence gaps, doing research) and politics (winning over key people, sequencing conversations, handling objections). Use after /clarify or when you need to turn a goal into concrete actions that make your case stronger AND navigate the people involved.
prd
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
file-todos
This skill should be used when managing the file-based todo tracking system in the .claude/todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.
synap-assistant
Manage a personal knowledge capture system. Use when the user wants to capture ideas, track todos, organize projects, review their synap, or mentions "synap", "brain dump", "capture this", "add to my list", "what's on my plate", "what should I focus on", or "daily review".
analysis-planning
Structure analysis approach before starting work. Use when receiving new analysis requests, breaking down complex questions into steps, or planning iterative analysis workflows.
launch-planner
Transform app ideas into shippable MVPs using a ship-fast, validate-early approach. Use when the user wants to: (1) Turn an idea into a PRD, (2) Generate Claude Code starter prompts, (3) Make product decisions during development, (4) Scope features for an MVP, (5) Stay focused on shipping vs. over-engineering, or (6) Get advice on building with Next.js, Supabase, and Vercel.
bd
Backlog management with the bd (beads) utility for issue tracking. Use when creating issues, claiming work, updating task status, closing completed work, or syncing the backlog with git.
roadmap-builder
Product roadmap prioritization and feature decision framework. Use when user asks about what to build next, whether to build a specific feature, roadmap prioritization, or feature validation. Helps challenge feature ideas, prevent feature creep, and maintain product focus based on stage-specific rules and impact vs effort analysis.
stakeholder-requirements-gathering
Structured requirements elicitation for analysis requests. Use when scoping new analysis projects, clarifying ambiguous business questions, or documenting analysis acceptance criteria with stakeholders.
track-management
Track lifecycle management patterns. Use when creating tracks, updating track status, generating track IDs, parsing plan files, or managing track metadata.
prd
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
generate-tasklist
開発作業のタスクリスト（tasklist.md）を生成します。このスキルは単独で使用することも、generate-working-docsから呼び出されることもあります。
interviewer
This skill conducts structured interviews to gather requirements. Auto-triggers when requirements are unclear, ambiguous, underspecified, when multiple valid approaches exist, when scope is undefined, or when Claude needs user input before proceeding. Use for discovery, clarification, decision-making, and stakeholder alignment.
ralph
Set up tasks for autonomous feature development. Use when starting a new feature that will be built task-by-task. Triggers on: ralph, set up ralph, start ralph, new ralph feature, ralph setup, plan feature. Chats through the feature idea, creates tasks with dependencies in progress.txt.
requirement-clarification
**AUTO-ACTIVATE when user mentions**: new feature, add functionality, implement,create, build, "I want to", unclear requirements, vague ideas.Asks 3 core questions to clarify requirements. Generates requirement documentswith clarity scores. Has templates for: priority features, search, forms, etc.Triggers: new feature, add, implement, create, unclear, vague, requirement
clarify
Start iterative requirement clarification loop. Use this skill when the user has a vague requirement and wants to clarify it through structured questioning. Transforms unclear requirements into precise, actionable specifications.
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
start-working
Continue work on the next priority from the issue tracking system. Use this skill when the user asks to start working, continue work, or pick up the next task. Follows the lightweight issue workflow (backlog → in-progress → done) with TDD emphasis and real-time progress tracking.
github-issues
**UNIVERSAL TRIGGER**: Use when user mentions GitHub issue URL or asks to read/work with GitHub issues.**CRITICAL RULE**: ALWAYS use `gh` CLI for GitHub issues, NEVER use WebFetch!Common patterns:- Any URL containing `github.com/.../issues/...`- "read issue #N", "show issue", "open task"- "прочитай issue", "покажи задачу", "открой issue #N"- "mark checkbox done", "complete step", "отметь пункт"- "create sub-issue", "add subtask", "создай подзадачу"Specific operations:📖 **Reading issues**:- "read issue https://github.com/owner/repo/issues/123"- "show task #45", "what's in issue #12"- "прочитай задачу", "покажи issue"✅ **Marking checkboxes**:- "mark step 1 as done", "complete checkbox"- "отметь пункт выполненным", "закрой этап 2"🔗 **Sub-issues**:- "create sub-issue for #123", "list sub-issues"- "создай подзадачу", "покажи дочерние issues"📝 **Issue management**:- "edit issue body", "add checkbox", "update task"- "close issue", "reopen issue"TRIGGERS: github.com/issues, github issue,
power-analysis
Analyze organizational power dynamics and develop realistic political strategies. Uses a Pfeffer-inspired realist lens - assumes self-interest drives behavior, past actions predict future actions, and formal authority often differs from real power. Use after /clarify when navigating complex stakeholder situations, building coalitions, or when you need to understand who really has power and what they'll actually do. Complements /executive-persuasion (which provides influence tactics) by mapping the political landscape first.
biometric-intelligence
Uses Oura ring data to make energy-aware decisions about scheduling, task prioritization, and recovery recommendations. Understands HRV, sleep quality, readiness scores, and their implications for productivity.
steering
作業指示毎の作業計画、タスクリストをドキュメントに記録するためのスキル。ユーザーからの指示をトリガーとした作業計画時、実装時、検証時に読み込む。
fpf-skillplanning-update-plan
Updates a PlanItem by recording variance, preserving the audit trail.
repo-help
Comprehensive guide to understanding and using this AI-assisted task management repository. Use this skill when users ask about how the repository works, what components are available, how to use agents/skills/prompts, or need guidance on the issue-tracking workflow.
dots
This skill should be used when the user mentions "dots", "dot", "tasks", "task", "todo", "issue", "track", "plan", "breakdown", or asks about task management. Provides guidance for using the dots CLI task tracker.
implementing-plan-phases
Executes implementation plan phases systematically, tracking progress with todos, managing feature branches, and verifying deliverables. Use when the user requests "implement phase N", "build the next phase", "continue implementation", "execute validation phase", or references implementation plans in requirements/implementation/. Handles branch creation, step-by-step execution, deliverable verification, and status updates.
user-story-acceptance-criteria
Writes and reviews user stories with acceptance criteria following standard categories. Use when creating user stories, defining acceptance criteria, or reviewing story completeness for GloboTicket features.
session-loader
Load feature specification and determine next task at session start. Use when user asks to "implement spec", "continue work", or "реализуй ТЗ". Finds spec file matching current branch and extracts next atomic task.
planner
Plan and coordinate tasks before implementation. Creates beads tasks separated by role (code-writer vs ui-ux-designer). Consults user until requirements are fully specified. Implementation cannot start until tasks are marked READY.
clarify
Structured discovery interview to understand a project or initiative deeply - both the substance (what you're proposing, what evidence you have, what gaps exist) and the politics (who decides, what drives them, how to navigate). Use when starting a new initiative, before planning, or when you need to think through both what you're trying to accomplish AND how to make it happen.
creating-implementation-plans
Creates structured implementation plans from feature requirements. Use when planning new features, multi-phase projects, or when the user asks for an implementation plan, build plan, or development roadmap.
lifeoptimizer
Solve general life challenges and optimize daily routines with structured approaches. Use when user needs help with time management, planning, decision-making, goal-setting, budgeting, or solving everyday life challenges with systematic solutions.
retrospective
Weekly retrospective - scans Done items from the past week, prompts reflection questions, captures one improvement action. Use when "weekly review", "run retrospective", "what did I ship this week", "reflect on my week", "end of week review".
project-dev-planner
專案開發工作流程管理，透過 5 階段結構化開發和智慧上下文載入節省 70-85% token。**觸發時機：**- 使用者輸入 'go init'（新專案 MVP 規劃）- 使用者輸入 'go'（開始/繼續開發）- 專案根目錄存在 TODO.md- 使用者提到「繼續開發」「專案進度」「模組化檢查」**核心功能：**- MVP 優先的互動式專案初始化- Token 優化的階段性開發（節省 70-85%）- 自動 conventional commits- 模組化健康度檢查
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
backlog-workflow
Project-agnostic workflow guidance for Backlog.md MCP task management. Covers search-first protocol, scope assessment, task creation standards, lifecycle management, and cross-session coordination.
guardrail-generator
Create flexible boundaries for projects - not rules or requirements, but bumpers that guide without constraining. Use when starting projects, when feeling overwhelmed by possibilities, or when needing structure without suffocation.
product-owner
Comprehensive product management guidance for planning, prioritizing, and growing digital products. Use when managing product backlog, conducting market research, defining product strategy, prioritizing features, writing user stories, analyzing competitors, setting product vision, planning releases, measuring success metrics, or making product decisions. Helps with competitive analysis, market sizing, user research, roadmap planning, OKR setting, and go-to-market strategy. Ideal for product owners, founders, and product managers building web and mobile applications.
plan-revision
规划修订导航。触发：用户通知"analysis-agent已分析完成"或需要plan-agent查看analysis-agent复审结果并修订预定清单时使用；评估analysis-agent分析结果并修订draft-plan.md。
milestone-tracker
Track project milestones with progress monitoring, deadline management, and stakeholder communication
beads-issue-tracking
Use this when working on tasks in this repo that require bd (beads) issue tracking, status updates, and the mandatory end-of-session push workflow.
win-the-day
Morning routine facilitator. Guides Ed through metrics, capture triage, and task clarity. Use at start of day with "win the day", "morning routine", "start my day", "let's get at it".
create-issue
This skill MUST be used instead of Atlassian MCP tools when the user asks to "create a Jira issue", "create a ticket", "add a Jira ticket", "make a new issue", "file a bug", "create a story", "add a task in Jira", or otherwise requests creating new Jira issues. ALWAYS use this skill for Jira issue creation - never use mcp__atlassian__createJiraIssue directly.
plan-mode
Guide for creating structured plans with numbered steps and quality gates
plan-to-issues
実装計画からGitHub Issuesを作成するスキル。実装計画テンプレートをエピックと子Issueに分解してGitHub Issuesとして起票する。「Issueを作りたい」「実装計画をIssue化したい」「エピックを作成したい」などのリクエスト時に使用。
executing-plans
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches