Total 50,510 skills, Project Management has 1846 skills
Showing 12 of 1846 skills
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. Part of the skills-for-java project
Create a TODO or initiative task in One Horizon. Use when asked "log this task", "create a todo", "track this small task", "create an initiative", "plan this project", or "start a roadmap initiative". For bugs or feature requests, use report-issue instead. Requires One Horizon MCP.
File Beads epics/issues from a finalized plan/spec AND do the polish pass (clarity, acceptance criteria, sizing, deps). Use when asked to create Beads from a plan/spec (OpenSpec, PRD, design doc), convert an external plan into Beads structure, or review/refine an existing Beads set.
Implement Beads work items from a bead id. Use when the user runs $beads-implement <bead-id> or asks to implement a bead/epic; if it is an epic, implement all sub-tasks, committing after each one and only interrupting when blocked or a decision is needed.
Write comprehensive commercial proposals for B2B technology consulting engagements. Integrate solution briefs, ROI/business cases, consulting pricing models (T&M, Fixed, Outcome-based, Retainer, Blended), team structure, governance, timeline, and terms. Output includes commercial-proposal.md and preliminary workplan-and-estimate.md that feeds into the PM suite's project-intake-and-charter skill. Use when creating proposals, writing SOWs, pricing engagements, or preparing commercial offers. Triggers on: proposal, commercial proposal, SOW, pricing, quote, engagement offer, commercial offer, statement of work.
Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"
Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"
Walk through a Jira task plan and interactively confirm assumptions, resolve open questions, and validate decisions — using progressive disclosure. Only asks questions relevant to the CURRENT phase or task being executed. Use when the user says "review the plan", "ask me questions", "clarify assumptions", "let's go through the questions", "grill me on the plan", "validate plan for PROJECT-1234", or anything about reviewing, questioning, or validating a task plan. Also triggered by the orchestrating-jira-workflow skill as Phase 3 of the pipeline, and re-invoked during Phase 5 before each task execution. Requires a task plan at docs/<TICKET_KEY>-tasks.md.
Translate discovered client pain points into high-level technology solution architectures for consulting engagements in Software Engineering, Data Platforms, and AI/ML. Produce solution briefs with phased roadmaps, effort estimations, team composition, and technology recommendations. Use when designing a pre-sale technical solution, creating a solution brief for a proposal, or when a prospect needs to understand what the engagement would look like before committing. This is the preventa técnica / solution engineering step.
Use this skill when you need to modify a project (add, delete, or modify files) and want to organically synchronize update_plan with CSV: Create a `{Task Name} TO DO list.csv` file in the project root directory, use TODO/IN_PROGRESS/DONE statuses to drive the pending/in_progress/completed status of the plan, advance tasks synchronously, and delete the file after all tasks are completed.
Sync project state with Linear — detect gaps, consolidate objectives, clean up, route to next action
Read and summarize an existing codebase before any design or implementation work begins. Use as a prerequisite when the project is not greenfield.