Planning, sales, accounting, legal, and project management (4.7K skills)
Explore ideas for products, content, names, strategies, technical approaches, or decisions. It frames the goal and constraints, generates distinct options, challenges assumptions and tradeoffs, then narrows the result to three strong choices with reasons and a next step.
Capture durable business rules, metric definitions, aliases, and conventions in reusable wiki pages. The workflow checks related pages and semantic-layer sources first, adds accurate cross-references, and avoids saving temporary requests or values that can quickly become outdated.
Forecast existing Azure spending or estimate prices for planned resources and workloads. The skill clarifies region, operating system, currency, and usage assumptions, then uses public or contract prices to support planning and comparisons.
Investigate actual Azure spending, bill changes, and cost spikes. Break down historical charges, examine AKS and AI service costs, and distinguish measured spending from inferred causes while identifying gaps in the available data.
Create or audit an agent team sitemap and product surface map, checking whether required concepts and validation steps are covered. It identifies omissions, adds task biases to protect important concerns, and records skipped or blocked concepts in a validation ledger.
Preserve a product team’s intent and decision context by extracting its user promise, audience, current decisions, open loops, and acceptance criteria. It also connects sitemap changes to product intent and records durable updates as memory events.
Prepare a sourced closeout proposal for one existing X1 coordination thread, using an explicit or strong decision from Minutes. X1 drafts the proposal for human review; the skill does not settle payments, contact people, or close the thread automatically.
Creates a qualitative project risk register using probability and impact ratings. It documents each risk’s cause, event, and impact, assigns an owner, sorts risks by score, and derives a mitigation plan focused on the highest priorities for review by qualified professionals.
Review an engagement report draft independently against supplied research, coverage, audience, and template materials. The critique identifies claims that need edits, missing evidence, material omissions, and unnecessary sensitive disclosures without rewriting the report.
Guide the creation and governance of Business Requirements Documents (BRDs) and Product Requirements Documents (PRDs) through discovery, definition, validation, and handoff. Use canonical templates, testable requirements, acceptance criteria, traceability links, quality reviews, and lifecycle records to produce actionable documents.
Standardize backlog handoffs from planning workflows to Azure DevOps (ADO) and GitHub. This reference provides shared HTML and Markdown templates, metadata and ID conventions, content sanitization rules, autonomy-tier vocabulary, and disclaimer placement guidance while leaving domain-specific fields to each planner.
Use phase-specific references to guide RAI planning, from initial scoping and risk classification to impact assessment, review, and backlog handoff. It provides focused guidance and templates for the phase at hand, including an optional Mural board setup.
Examine a confirmed task, decision, plan, or artifact through adaptive, skeptical questions. The exchange surfaces assumptions, evidence gaps, and unresolved choices, then records the discussion without turning it into a review or solution session.
Creates or assesses a testable business outcome hypothesis: who should benefit, what measurable result may change, and by when. It connects evidence, baselines, targets, and indicators so teams can judge readiness before investing.
Create weekly engagement reports grounded in primary sources such as meetings, email, and boards. Organize completed, ongoing, blocked, and upcoming work for the intended audience, review the claims, and optionally prepare an Outlook draft after approval.
Provides shared conventions for discovering, reviewing, planning, and executing backlog work across Azure DevOps, GitHub, and Jira. It helps assess duplicates and item quality, apply review gates and sanitization rules, and includes guidance for Azure DevOps pull requests and build information.
Analyze RFI, RFP, tender, bid, and questionnaire items, connect them to approved business or product evidence, and prepare qualified responses for internal review. It tracks coverage and evidence gaps without treating drafts as approved or externally releasable.
Use a Python command-line tool to search Jira with JQL, inspect issues, create or update work items, change workflow status, manage comments, and discover required fields. It supports Jira Cloud and Jira Server or Data Center authentication.
Guide a Design Thinking coach through a consistent coaching approach, quality and fidelity expectations, transitions across nine methods, and session-state recovery. It also describes an optional workflow for creating a canonical slide deck and customer cards.
Plan backlog work in Azure DevOps, GitHub, or Jira by finding candidate items, reviewing priorities, preparing sprint plans, or resuming interrupted planning. It records recommendations and handoff details in planning files without changing tracker items.
Use this skill to create one work item or execute a reviewed handoff in Azure DevOps, GitHub, or Jira. It validates the confirmed destination, supports dry runs and resumable batches, and records each attempted change. Tracker updates require an available write surface and appropriate access.
Map how personal data is collected, used, shared, stored, retained, and deleted, then use privacy framework references to organize risks, controls, and evidence. The guidance also helps assess when a deeper review such as a DPIA may be needed.
Turn a concrete PRD into a validated hierarchy of work items for Azure DevOps, GitHub, or Jira. The skill checks existing context and supported types through read-only discovery, then produces planning files and a reviewable handoff for a separate execution step.
Prepare and present broker order tickets, record the user’s explicit yes, and track order results and fills. The workflow uses paper trading by default and requires a separate permission approval before an order is sent.