Productivity Skills

Product planning skill for BMAD. Use for bmad:prd, bmad:tech-spec, and bmad:prioritize to convert discovery into executable requirements.

Product discovery and analysis skill for BMAD. Use for bmad:product-brief, bmad:research, and bmad:brainstorm to clarify user needs, market context, and problem scope.

Sprint planning skill for BMAD. Use for bmad:sprint-plan and bmad:create-story to build sprint scope and implementation-ready stories.

Implement incident management processes and escalation procedures. Configure on-call schedules and post-incident reviews. Use when managing production incidents.

Implement disaster recovery strategies and runbooks. Configure RPO/RTO targets and failover procedures. Use when planning for business continuity.

Builds consulting pricing models, rate cards, engagement economics, and commercial terms. Use when structuring fees (fixed, time and materials, value-based, retainer, outcome-based, or hybrid), building or defending a rate card, modeling margins and team leverage, setting payment schedules and liability caps, planning discount and negotiation strategy, or drafting the commercial sections of a proposal or SOW. Covers model-selection logic, fully loaded cost buildup, realization, and value-case construction.

Conducts commercial, operational, financial, strategic, and technology due diligence for M&A, investment, partnership, and vendor decisions, from scoping through risk synthesis to a proceed/no-proceed recommendation. Use when assessing an acquisition target, running a quality-of-earnings analysis, normalizing working capital, testing revenue quality and customer concentration, reviewing a tech stack and IP, quantifying synergies, or planning post-merger integration. Triggers on keywords like due diligence, QoE, data room, red flags, synergy, deal risk, and investment recommendation.

Runs the first weeks of a consulting engagement, from signed contract to a project with real momentum. Covers kickoff design, stakeholder mapping, discovery planning, interview guides, and the operating cadences that hold the work together. Use when launching a new engagement, onboarding a client, designing a kickoff workshop, building a discovery plan or interview guide, standing up workstreams, or resetting a stalled project that never got proper alignment.

Produces consulting-grade client deliverables (written reports and executive presentations) built on structured narrative (SCQA/SCR), the pyramid principle, action-titled sections, and evidence-backed recommendations. Use when creating strategic assessments, board decks, due diligence reports, PE investment committee (IC) memos, steering committee updates, recommendation documents, or any formal analysis that must drive an executive decision. Covers storylining, audience adaptation, exhibit design, and the choice between a document and a deck.

Consulting engagement lifecycle in one skill: strategy and framework analysis, financial modeling, proposals and pricing, implementation planning, due diligence, change management, governance, and client deliverables. Use for any management-consulting task, then load the matching reference file below.

Translates a strategic recommendation into an investable, executable plan through option development, business case construction, roadmap design, and detailed implementation planning. Use when a recommendation exists and the work is to make it real: generating and scoring structurally different options, building financial projections with NPV and sensitivity analysis, sequencing phased roadmaps with dependencies, and defining workstreams, governance, RACI, and resourcing. Covers the full arc from "we have a recommendation" to "here is exactly how we execute it.

Builds financial models and business cases (ROI, NPV, IRR, payback, DCF valuation, scenario analysis, TCO, break-even) that support a specific investment decision. Use when developing an investment recommendation, comparing strategic options, quantifying the value of an initiative, building a go/no-go business case, running cost-benefit analysis, sizing total cost of ownership for build-vs-buy, or valuing a business unit. Covers standard workflows (ROI, cash flow projection, break-even, DCF) and advanced techniques (EVA, MIRR, real options, Monte Carlo, discount rate selection, AI and technology investment patterns).

Designs and runs organizational change programs: transformation planning, stakeholder engagement, resistance management, communication strategy, training design, and adoption measurement. Use when planning or delivering any organizational change (digital transformation, AI adoption, merger integration, culture shift, new operating model, ERP or system rollout) and when the ask is a change approach, stakeholder map, resistance playbook, communication plan, champion network, or adoption scorecard. Diagnoses where adoption stalls and prescribes the intervention rather than issuing generic advice.

Executes consulting engagement closeout: deliverable handover, client acceptance sign-off, knowledge transfer, benefits tracking handover, lessons learned, financial reconciliation, and administrative wrap-up. Use when completing or terminating a consulting engagement, transitioning a project into business-as-usual, running a closure retrospective, handing benefits measurement to the client, or planning stakeholder transition before the team departs. Covers successful completion, early termination, and regulated-industry closeout requirements.

Set up and run the oversight structure for a consulting engagement: governance tiering, RACI and decision rights, steering committee cadence, stage gates, RAG status reporting, risk and issue registers, and closure handback. Use when standing up engagement governance, defining who decides what, right-sizing a PMO, building a risk register, writing a steering committee status report, or scoring and tracking project health. Covers the management lifecycle from charter sign-off through closure. For the delivery plan itself (workstreams, phasing, business case), see implementation-planning.

Designs organizational structures, operating models, role architectures, and transition plans that connect structure to strategy. Use when restructuring a business or function, choosing an operating model (functional, divisional, matrix, agile), defining reporting lines and spans of control, building job families and grading frameworks, allocating decision rights, or sequencing a reorganization and its change management. Covers strategic requirements, current-state diagnosis, future-state design, role definition, transition planning, and governance.

Design and facilitate consulting workshops: strategy offsites, design thinking sessions, innovation sprints, and discovery workshops. Use when planning client-facing facilitated sessions, running stakeholder alignment or prioritization exercises, designing working sessions for strategy development, or building facilitation guides and pre-work. Covers objective-setting, participant planning, methodology selection, agenda design, facilitation technique, and post-workshop follow-through.

Day Open protocol. Collects yesterday's commits, issues, notes, calendar, bot QA, Scout, world events — builds DayPlan and compact dashboard.

Decompose work into stages with physical artifacts and acceptance checklists. Gap detector. Use when opening a WP ≥3h (open-loop/problem-framing) or on explicit request to break into stages. Executes R29 Decomposer role.

Knowledge Extraction — captures and routes knowledge at work boundaries. Use when you discover a pattern, make a decision, find a distinction, or complete a sub-task.

Peer-сессия DP.SC.154 где Kimi = писатель, Claude = напарник. Запускается простой фразой. Включает ОРЗ Opening и Closing, turn-loop, эскалации, Decision Gate (зафиксировать vs реализовать → ревью → проверить → задеплоить), отложенную финализацию и верификацию.

Многотуровый диалог писателя (Claude) с напарником (Kimi по умолчанию, Codex — второй вендор) по задаче пилота (DP.SC.154). Ведёт turn-loop, обнаруживает CONSENSUS/ESCALATE, после консенсуса — Decision Gate (зафиксировать vs реализовать → ревью → проверить → задеплоить), синтезирует report.md через Agent tool.

ADI-cycle structured reasoning (Abduction-Deduction-Induction-Audit-Decide). Use for complex decisions when multiple hypotheses need to be considered.

Helps beginners find their first AGENTIC project through pain point identification. Guides through questioning, analysis, project suggestion, and folder setup. Use when someone asks 'what project should I build?' or 'help me get started with Claude Code'.

Conduct deep adaptive interviews to extract and organize knowledge into structured files and folders. Use when user says "interview me about X", "deep interview", "extract my knowledge", "build knowledge base from interview", "ask me questions about X", or wants to systematically capture expertise on any topic through guided questioning.

Inject creative absurdity to break AI pattern-thinking before creative tasks. Randomly samples surreal micro-stories to spark unconventional thinking. Use before brainstorming, naming, writing, or any task needing fresh perspective.

Decision tree for selecting pump type based on flow, head, and fluid properties

Systematic workflow for fluid dynamics analysis from problem setup to validation

FEA workflow for pump casings and impellers under fluid loads

>- Turn a raw product idea into build-ready docs — one doc per EPIC with locked decisions, exact API contracts, a story-by-story priority plan, and an execute.md handoff Claude can build from across sessions. Gets the clarity by interrogating the user through a roster of expert personas that grill, counter, and refuse to flatter. Use to ideate, validate, scope, architect, or plan a product, feature, startup, or app before any code is written. Invoke by persona name or acronym to summon one expert, or with no argument to run the full lifecycle end to end.

ADR template, database selection, capacity planning ve scalability.

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

Coordinate security incident response efforts. Includes classification, playbook generation, evidence gathering, and remediation planning. Validates response strategies against best practices.

This skill should be used when creating or updating PROJECT.md files, planning sprints, defining project goals, or managing project scope. It provides templates and best practices for PROJECT.md-first development.

Comprehensive Scrum Master assistant for sprint planning, backlog grooming, retrospectives, capacity planning, and daily standups with intelligent context-aware reporting

> Adversarial code/plan/design review by a senior dev who hates what you built. Use this skill whenever the user asks for a hostile, brutal, or adversarial review — phrases like "tear this apart", "what's wrong with this", "pretend you hate this", "roast my code", "devil's advocate", "worst-case critique", "what am I missing", "what would a critic say", or "stress-test this plan" should all trigger it. Also use proactively when the user seems too confident about a piece of code or a design decision and would benefit from someone pushing back hard. The output is severity-ranked criticisms with concrete fixes — not a PR checklist, but a genuine attempt to break the thing before reality does.

> Behavioral modifier that applies senior PM-level critical evaluation to user requests. Use when the user invokes /critical-mode, or asks for "critical mode", "pm mode", "challenge my assumptions", "push back on this", "be my devil's advocate", or wants the assistant to actively question whether a request is the right thing to do before executing. aggressive (maximum scrutiny). Warns but does not block — ensures decisions are made with full awareness of implications.

> The project's institutional memory and decision authority. Acts as an autonomous representative of the project — its goals, architecture, conventions, constraints, and intent. Use this skill whenever the active agent or another skill needs clarification about "ask the ambassador", "check with the ambassador", "what does the project want", "what's the project's stance on", or when any skill produces clarifying questions that the user redirects here. Also triggers when the user says "let the ambassador decide", "the ambassador knows", "don't ask me, ask the project", or similar delegation phrases. Use proactively when you're about to ask the user a question about project intent, conventions, or architecture — consult the ambassador first. If invoked without a prompt, performs a project knowledge audit.

>-

Create branching, draggable HTML mind maps and concept maps for capturing brainstorms, mapping knowledge structures, exploring debugging hypotheses, or organizing nested ideas. Always include a Submit button (calls `submitToClaude`) to send the captured structure back to the agent for next steps. Use whenever the user wants to capture, organize, or explore branching ideas, hypotheses, knowledge structures, or any tree/graph-shaped thinking — especially when they say "brainstorm", "map out", "explore", or "what if".

Create rich HTML documents for project specs, implementation plans, design exploration, RFCs, and brainstorming. Use whenever the user asks for a spec, plan, RFC, design doc, brainstorm, or wants to explore approaches/options/alternatives — even when they don't explicitly say "HTML". Strongly prefer HTML over markdown for any planning artifact longer than a screen, especially when the artifact will be shared with reviewers or fed back to the agent for implementation.

>- Sets up the per-session local receiver and `Monitor` for interactive html-skills artifacts so user submissions arrive as session notifications instead of as copy-paste round-trips. Other html-skills interactive skills (html-mind-map, html-throwaway-editor, html-brainstorm-grid, html-comparison-matrix, html-interactive-playground, html-design-prototypes, html-testing-checklist) invoke this skill from their pre-flight block, BEFORE writing the HTML artifact. Idempotent — safe to invoke every time. Returns a localhost URL the parent skill injects as `window.__CLAUDE_SUBMIT_URL__` in the artifact. Don't invoke unprompted in unrelated conversations — this only fires when an interactive html-skills artifact is about to be produced.

Generate thorough, interactive HTML testing checklists that help developers and testers systematically verify software — a real test plan organized into end-to-end flows, with a prominent progress bar, pass/fail/blocked step states, filter and search navigation, and syntax-highlighted code and command snippets. Always ends with a Submit button (calls `submitToClaude`) so results come back to the agent for failure triage and fixes. Use whenever the user wants to test, QA, verify, or validate a change, feature, release, PR, or bug-fix batch — "help me test this", "test plan", "QA checklist", "verification checklist", "smoke-test list", "regression checklist". Bug lists in issue trackers (Monday, Linear, Jira, GitHub…) are natural input — render the open items as a two-way checklist whose rows keep ticket ids, and offer to write verdicts back to the tracker after Submit. Every embedded snippet passes a redaction step so credential-shaped values never land in the artifact.

Create HTML timelines and roadmaps with status pills, dependency arrows, and milestone markers — for quarterly planning, project retrospectives, release histories, incident timelines, sprint visualizations. Use whenever the user wants to visualize a sequence of events over time, a plan, a roadmap, a release schedule, or look back at how a project unfolded. Reach for this whenever the explanation has a clear time axis, even if the user doesn't say "timeline".

Integrate raw product demo recordings into agent-created videos, including crop decisions, zoom preservation, camera swipe transitions, UI readability checks, and timing around narration. Use when a user provides screen recordings, product walkthrough clips, SaaS demos, app footage, browser recordings, or asks to transition into/out of product demo footage.

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

> Entry point for reading PANews cryptocurrency / blockchain news, market narratives, and Polymarket smart money leaderboards. reading specific articles, browsing columns / series / community topics, industry events & conferences, event calendar, platform hot searches and editorial picks, latest smart money boards, board highlights, and board comparisons.