Productivity skills

Browse reusable Agent Skills, each with a clear purpose and practical guidance.

bmad-help

Orchestration spine and "what do I do next?" router for the BMAD Planning & Orchestrator plugin. Detects current planning state by scanning the output folder for which artifacts exist (project-context.md, decision-log.md, product-brief, prd/tech-spec, architecture, ux, epics, stories), infers the current phase and track, then recommends the next BMAD skill to run — skipping optional phases (Analysis is always optional; UX only when there is a UI). Use when the user asks "what's next", "what do I do next", "where am I", "what's my status", "continue", "resume planning", "which skill should I run", "what BMAD step is next", or types "/bmad-help" / "/status". Auto-invoke at the start of any BMAD planning session to orient. This skill ROUTES only — it never writes planning documents itself.

460 repo starsObserved in 1 repos
Productivity
GitHub

bmad-parallel-plan

Turns a sequential, ready-for-dev story backlog into conflict-free CONCURRENT WAVES. Builds a dependency DAG from epic order, per-story dependency maps, and Owned File/Module Scope overlaps, then topologically sorts it into parallel waves of mutually disjoint, dependency-satisfied stories (capped by maxParallel), and emits a parallelization-plan.md with per-story git-worktree branch names and an ordered merge sequence. Use when the user says "plan parallel work", "which stories can run in parallel", "parallelize the backlog", "build the wave plan", "parallelization plan", "conflict-free workstreams", "what can we run concurrently", "split into worktrees", "dependency graph for the stories", "merge order", or "how do I fan this backlog out to multiple dev agents". Run AFTER stories are ready-for-dev (scrum-master) and an architecture exists. This skill PLANS parallelism only — it does NOT run agents, spawn worktrees, write code, run tests, or perform git operations.

460 repo starsObserved in 1 repos
Productivity
GitHub

bmad-prd

PRD facilitator (John the PM). Authors and maintains the Product Requirements Document — functional requirements (FR-###), non-functional requirements (NFR-###), an epics outline, user stories, acceptance criteria, and MoSCoW/RICE prioritization. Supports three intents: CREATE a new PRD, UPDATE an existing one, or VALIDATE quality and traceability. Emits prd.md plus addendum.md (overflow/notes) and appends decisions to decision-log.md. Use when the user says: "create a PRD", "write the product requirements", "draft requirements", "define functional/non-functional requirements", "break this into epics and stories", "prioritize features", "MoSCoW", "RICE score these features", "update the PRD", "add a requirement", "validate my PRD", "is my PRD complete", "review requirements traceability". This is PLANNING only — it never writes application code, runs tests, lints, or builds.

460 repo starsObserved in 1 repos
Productivity
GitHub

bmad-readiness-check

SOLUTIONING GATE — validates cohesion across planning artifacts before any implementation begins. Cross-references PRD (or tech-spec), architecture document, and epics/stories for coverage consistency and missing pieces. Returns a verdict of PASS, CONCERNS, or FAIL with specifics. Does NOT touch code. Use when the user says: - "check if we're ready to build" / "are we ready to implement?" - "validate planning" / "gate check" / "readiness check" - "run the solutioning gate" / "check implementation readiness" - "is the architecture complete?" / "do requirements match architecture?" - "sign off on planning" / "planning done, check it" - "validate PRD against architecture" / "cross-reference planning docs" Intents supported: Validate (primary). Track-adaptive: works for Quick Flow (tech-spec + architecture), BMad Method (PRD + architecture + epics), and Enterprise (all of the above + optional security/DevOps addenda).

460 repo starsObserved in 1 repos
Productivity
GitHub

bmad-sprint-planning

Orchestration handoff bridge: emits and maintains sprint-status.yaml as the project's sequencing system-of-record. Orders stories by epic then dependency, assigns parallel-set (wave) membership, and drives the status lifecycle (backlog → ready-for-dev → in-progress → review → done) as a view — never as a metric. Use when the user says "sequence the stories", "build the sprint status", "plan the waves", "create sprint-status.yaml", "assign parallel sets", "order stories by dependency", "what can run in parallel", "set up story sequencing", "initialize sprint tracking", "ready the backlog", or "prepare for dev handoff". Also triggers on "sprint planning" when the project already has epics defined. SCOPE: SEQUENCING AND ORCHESTRATION ONLY. No velocity, no burndown, no committed points, no coverage metrics. Capacity is expressed as wave width (concurrent story count), not points. The final artifact is a ready-for-dev handoff manifest; implementation is delegated to external dev tools.

460 repo starsObserved in 1 repos
Productivity
GitHub

bmad-tech-spec

Quick Flow lightweight technical specification for small-scope work (1-15 stories). Replaces the full PRD + architecture pair when scope is small and requirements are clear. Produces bmad-output/tech-spec.md as the single planning artifact before story creation. Use when the user says: "write a tech spec", "create a technical specification", "I need a tech spec for this feature", "quick spec", "small project spec", "we don't need a full PRD", "just a tech spec", "spec out this change", "document this feature". QUICK FLOW TRACK ONLY (1-15 stories). If scope grows beyond ~15 stories or involves multiple teams / external integrations at scale, stop and redirect to bmad-prd + bmad-architecture instead — those skills are built for that complexity. Supports three intents: Create (new spec), Update (revise an existing tech-spec.md), Validate (review a draft for completeness against BMAD criteria).

460 repo starsObserved in 1 repos
Productivity
GitHub

mcaf-agile-delivery

Apply MCAF agile-delivery guidance for backlog quality, roles, ceremonies, and engineering feedback. Use when defining how the team plans, tracks work, and turns feedback into durable improvements. USE FOR: the team needs backlog, ceremony, role, or feedback-loop rules; delivery process is vague, too heavy, or living only in chat; recurring team pain needs to become durable. DO NOT USE FOR: repo governance that belongs in AGENTS.md; feature planning for one specific feature doc. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

459 repo starsObserved in 1 repos
Productivity
GitHub

fusion-plan

Produce a high-confidence, CONCISE implementation / architecture / strategy PLAN that follows the OMC plan system end to end. It first runs OMC's real requirements interview (auto-chains the `omc-plan` skill: one question at a time, explore-first, Analyst consult) to produce an initial plan in `.omc/plans/`, then DEEPENS that plan with a 3-round ITERATIVE fusion loop — each round an Opus 4.8 panelist (Agent subagent) and a GPT-5.5 panelist (via codex) critique/improve it IN PARALLEL and BLIND, then Opus 4.8 (the orchestrator) judges and synthesizes one tighter plan that seeds the next round, stopping early on convergence. Writes the final dense plan back to the same `.omc/plans/<slug>.md`, then offers the OMC handoff (`/omc-plan --review` → `/team` or `/ralph`). Use for high-stakes planning, architecture decisions, strategy calls, and hard debugging — especially when the user runs /plan or asks how to approach a non-trivial build. Reuses the `fusion` skill's run_codex.sh + judge rubric. NOT for trivial tasks (single pass is enough).

457 repo starsObserved in 1 repos
Productivity
GitHub

meeting-notes-to-actions

Convert meeting notes into owners, action items, decisions, and follow-up messages.

455 repo starsObserved in 1 repos
Productivity
GitHub

instructional-coaching-conversation-guide

Generate a coaching conversation guide with questions, protocols, and follow-up actions for a teaching focus. Use when preparing for coaching sessions, mentoring, or peer feedback conversations.

454 repo starsObserved in 5 repos
Productivity
GitHub