PRDs & Specs Agent Skills

Guide product managers through a comprehensive strategy session covering positioning, discovery, and roadmap planning to move from vague direction to validated strategy.

Run a user story mapping workshop with adaptive questions and a structured map output, generating backbone activities, user tasks, and release slices for a workflow.

Articulate a compelling north-star product vision that aligns teams and guides strategic design decisions.

Analyzes dependencies between stories, code modules, tickets, or specs to compute an optimal implementation order with parallel batches, cycle detection, and critical path analysis.

Guides users through a structured interview to clarify their AI agent idea and produces an Agent Requirement Document (ARD).

Guides a structured requirements pipeline from topic intake through brainstorming, spec and plan writing, user review, SRS generation, validation, and improvement reporting.

Generates an IEEE 830 software requirements specification from raw client input through structured clarification rounds and a review gate.

Guides a structured requirements pipeline from topic intake through brainstorming, spec writing, planning, user review, SRS generation, validation, and improvement reporting.

Turns raw client requirements into an IEEE 830 software requirements specification through structured clarification and gap analysis.

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

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

Designs system architecture and translates requirements into actionable plans, creating PRDs and tasks via Task Copilot.

Drafts a GitHub issue with YAML frontmatter and checkboxes, writing it to a local file for review.

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

Turns a raw idea into four linked planning files through a five-phase pipeline: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased execution plan with kill criteria.

Erstellt Entwürfe für Agio und Kapitalerhöhungsstrukturen in der Corporate-Praxis, inklusive Anträgen, Begründung und Anlagenlogik.

Prüft App-AGB auf typische Risiken, trennt Einbeziehung, Transparenz und Inhaltskontrolle, und liefert Klauselampel, Redline und Ersatzformulierungen mit gerichtsfester Begründung.

Builds an investor, product, or sales pitch deck as a PPTX file from a written brief, extracting fundamentals, flagging gaps as TODOs, drafting slides with speaker notes, and rendering with python-pptx.

Turns a raw idea, brain dump, or conversation into a complete PRD with mandatory acceptance criteria and measurable success metrics. Extracts the problem, target users, and jobs-to-be-done, runs a quick competitive scan (web if available, logged as a gap if not), drafts the full PRD (problem, personas, user stories.

Creates product backlog items in Why-What-Acceptance format, producing independent, valuable, testable items with strategic context.

Evaluates iOS, macOS, tvOS, watchOS, and visionOS app code against Apple's App Store Review Guidelines to identify potential rejection issues before submission.

Guides a structured requirements workflow from topic intake through brainstorming, spec and plan writing, user review, SRS generation, validation, and improvement reporting.

Guides strategic product decisions, pricing, backlog prioritization, and trend intelligence, routing tasks to specialized sub-skills.

Creates an approval-gated product requirements document or decomposes an approved PRD into a traceable roadmap, covering product-level problems, new initiatives, multi-feature scope, PRDs, release outcomes, and roadmap planning.

Write and refine user stories using INVEST criteria, the 'As a X, I want Y, so that Z' format, Gherkin acceptance criteria, definition of ready, anti-patterns, and a review checklist.

Interviews the user in depth about a plan, probing technical implementation, UI/UX, risks, tradeoffs, and missing decisions before writing or refining a spec.

Breaks applications or features into thin vertical user-story slices with clear acceptance criteria and user-observable value, suitable for backlog planning and feature decomposition.

Exports a platform feature as a product constitution and data reference, including data model, API contracts, and acceptance criteria, for use in AI prototyping tools.

Guides a structured software requirements specification workflow from topic intake through brainstorming, spec writing, planning, review, SRS generation, validation, and improvement reporting.

Runs a structured, multi-round brainstorm to capture actors, features, scope, constraints, and business rules for a project before writing a spec.

Stress-tests a plan against the project's domain model and documented decisions, sharpening terminology and updating DOMAIN.md and ADRs inline as decisions crystallize.

Verifies each step of a rough implementation plan against source code and current documentation, attaching proof and marking steps as verified or unverified.