Total 53,577 skills, Project Management has 1942 skills
Showing 12 of 1942 skills
Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security/data/migration/integration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straightforward fixes, active debugging, code review, or implementation requests whose acceptance conditions are already clear unless the user explicitly invokes this skill.
Research and discovery workflow for document deliverables — competitive analyses, architecture comparisons, ADR scaffolding, literature reviews, vendor evaluations. No TDD requirement. Phases: gathering → synthesizing → completed. Triggers: 'discover', 'research', 'explore topic', or discover.
Adversarially stress-test a plan or design until every load-bearing assumption is defended or the plan is rejected. Use when the user wants to be grilled, pressure-tested, or "grill-me-thermonuclear". NOT for generative brainstorming, affirmation, light polish, or executing an already-settled plan.
Manage Jira issues, sprints, and epics using the jira CLI (ankitpokhrel/jira-cli). Use when asked to create, view, edit, list, move, assign, comment on, link, or delete Jira issues. Also use for sprint operations (list sprints, view current sprint, add issues to sprints) and epic operations (create epics, add/remove issues). Triggers on any Jira-related task, ticket management, sprint planning, or board workflow request.
Start-Stop-Continue retrospective identifying what to Start doing, Stop doing, and Continue doing. Use for sprint retros, personal reflection, team process reviews, or habit audits.
Separate WHAT from HOW before planning. Clarify goals, explore approaches, capture structured design decisions. Triggers: brainstorm, explore idea, clarify goal, idea phase.
Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.
creates draft task file in .specs/tasks/draft/ with original user intent
FORGE Quick Track — Spec + direct implementation for bug fixes and small changes. Usage: /forge-quick-spec "change description"
Semantic validation patterns for PROJECT.md alignment (GOALS, SCOPE, CONSTRAINTS, ARCHITECTURE)
Unified prompt engineering and requirements planning. Use when exploring ideas, improving prompts, creating PRDs, generating task breakdowns, or iterating on existing plans. Includes Jira integration for creating subtasks from plans.
Provides a comprehensive status overview of the Conductor project. Use when the user wants to know the current progress, active tasks, next steps, or overall health of the project tracks and plans.