PRDs & Specs Agent Skills

Writes user-focused acceptance criteria for Jira stories using Given/When/Then scenarios, and updates the ticket via the Atlassian MCP server.

Routes product-discovery work into the right stage — opportunity brief, research, PRD, tickets, or outcome review — and hands off to the matching sub-skill.

Runs a structured product-discovery interview and publishes a two-page Opportunity Brief to Confluence, covering business objective, customer, problem, success metric, alternatives, assumptions, and open questions.

Analyzes requirements and produces four artifact files: requirements.md, user-stories.md, acceptance-criteria.md, and business-rules.md, with optional loading from SRS workflow artifacts.

Creates a machine-readable phased JSON plan bundle from a spec or feature description, producing a compact master manifest plus per-phase step files for resumable execution.

Guides a structured brainstorm that surfaces user ideas, explores directions, and produces a spec and report for later planning.

Generates an IEEE 830 software requirements specification from raw client input, guiding users through structured clarification rounds and producing a compliant document.

Generate a structured specification document before writing implementation code, validating scope, drafting specs, and registering them in the project.

Synthesizes the current conversation and codebase context into a structured PRD and publishes it to the project issue tracker with a triage label.

Turns the current conversation context and codebase understanding into a PRD and publishes it to the project issue tracker with a triage label.

Runs a structured interview that stress-tests a plan against the project's domain model, sharpens terminology, and updates CONTEXT.md and ADRs inline as decisions are made.

Turns a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects, with self-contained context briefs, adversarial review, and dependency graphs.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Opens plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use when presenting a plan for review, or when feedback like "move this, change that" is easier pointed at than typed.

Creates agent company packages that conform to the Agent Companies specification, either from scratch or by analyzing an existing repository.

Breaks a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/.

Guides a structured interview and codebase exploration to produce a PRD, then submits it as a GitHub issue.

Guides collaborative dialogue to turn ideas into designs and specs, exploring intent and requirements before any implementation.

Breaks a product requirements document into independently-grabbable GitHub issues using vertical slices, with user approval before creation.

Resolves legacy references to the product-manager capability by routing to the current runtime agent or skill.

Generates a structured Product Requirements Document for the MÄÄK dating app, with clarifying questions, right-sized user stories, and verifiable acceptance criteria.

Turns product ideas into structured specs for AI tools or stakeholder review, with quick feature specs and full project scopes.

Convenes a council of specialized agents to debate important decisions, synthesizing independent perspectives into a structured recommendation and optional spec document.

Guides the agent through structured protocols for writing technical specifications, implementation plans, and summaries, with file naming and task directory conventions.

Turns a mature product plan into a rough implementation plan with high-level steps, maturity and verification marks, and a risks section.

Turns a raw feature or project idea into a structured product plan document covering goals, audience, requirements, and constraints, with a maturity-tracking workflow.

Guides writing Korean government funding program business plans (사업계획서) from an evaluator's perspective, covering structure, scoring emphasis, and writing principles.

Enter explore mode to think through ideas, investigate problems, and clarify requirements before implementation, with optional OpenSpec artifact creation.

Guides the agent to act as a product manager, collecting context, proposing three requirement plans (bug fix, new feature, iteration), scoring them by ROI, and recommending one with an MVP slice and timeline.

Define o produto Auri, um assistente de voz inteligente baseado em Alexa e Claude, incluindo visão, persona, arquitetura AWS, planos de preços, roadmap e estratégia de mercado.

Identify, assess, and mitigate project risks across technical, scope, dependency, and timeline categories using a structured register and escalation rules.

Transforms a raw product idea into four planning files: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased execution plan with kill criteria.

Analyzes development requirements and generates structured acceptance criteria for AEM Edge Delivery Services tasks, including task breakdowns and edge case identification.

Build a minimum viable product using the minimalist entrepreneur approach: manual first, then processized, then productized.

Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery planning.

Create a Geoffrey Moore-style positioning statement to clarify target customers, unmet needs, product category, and differentiation from alternatives.