Results for “feature-requests”

Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists.

Guides a structured interview and repository research to clarify feature requirements, classify scope, and produce context artifacts for approval before design.

Run a structured discovery interview and produce a complete, developer-ready Product Requirements Document. Load when the user asks to write a PRD, create product requirements, document a feature, define user stories with acceptance criteria, or turn a rough idea into a formal product requirements document. Also triggers on "document this feature", "write requirements for", "create a one-pager", "turn this into a PRD", "I need a PRD for", or any request to produce a structured product document for stakeholder alignment or engineering handoff. Supports Full PRD, Lean PRD, and One-Pager formats. Note: for executable feature specifications (FRs, NFRs, ACs as Given/When/Then consumable by AI coding agents), route to `feature-spec` instead — PRDs frame the product, feature-specs encode the implementable contract.

Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

Designs an approval-gated feature specification from approved requirements, covering architecture decisions, component boundaries, quality constraints, and definition of done.

This skill should be used when the user asks to "plan a feature", "create PRD", "interview me about requirements", "define stories", "write a spec", "break down feature into tasks", "create implementation plan", "help me scope this feature", "what questions should I answer", or discusses feature planning. Covers the PRD interview process, spec structure, story atomization, and 4-phase workflow from idea to Dex tasks.

Identify missing features in a project, prioritize them, and create detailed GitHub issues with specifications.

Creates a GitHub issue from a specification file using a feature request template, checking for existing issues first.

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

Generate Product Requirements Documents through structured conversation for any project. Use when starting a new feature, documenting requirements, creating specs before implementation, or needing clarity on scope and success criteria.

Structures product requirements into a single-page spec with problem, success metrics, scope, user stories, design notes, and rollout plan.

Generates a structured Product Requirements Document (PRD) for a new feature, including clarifying questions, user stories, functional requirements, and success metrics.

Loop feature-interviews over a brainstorm idea set and consolidate survivors into the roadmap

Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

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.

Product execution specialist for SaaS, apps, AI tools, and internal software products. Trigger when user requests 'build SaaS', 'define features', 'create user flow', 'scope MVP', 'prepare build package', 'software product', 'app definition', or 'PRD creation'.

Translates stakeholder feature requests into validated outcome statements before any work is committed. Use this skill — proactively and without waiting to be asked — whenever a stakeholder, exec, or customer arrives with a pre-packaged solution: "we need a dashboard", "add a Slack notification", "build an export feature", "create a report", "let's add a filter", "can we just add X". Also triggers for: "how do I push back on this request", "what outcome does this feature solve", "outcome vs output", "outcomes not features", "what are we really trying to achieve", "we're being a feature factory", "I need to reframe this as a problem", "the stakeholder is pushing a specific solution", "discovery before delivery", "assumption testing", "translate this request into an outcome", "ship outcomes not features". Runs the 'One Framework. Four Questions.' protocol (Liatti + Cagan + Torres): Behavior Change → Assumption Test → Cheapest Test → Success Metric. Produces an Outcome Brief with embedded AI prompts ready to pas