Results for “feature-definition”

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

Creates detailed technical implementation plans for features based on a Feature PRD, including system architecture, database schema, API design, and frontend component hierarchy.

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

prd-writer

Rank a backlog of feature ideas by impact, effort, risk, and strategic alignment to identify the top 5 to pursue.

Categorize, evaluate, and prioritize customer feature requests against product goals using strategic alignment, impact, effort, and risk analysis.

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

Evaluate feature investments using revenue impact, cost structure, ROI, and strategic value to make data-driven build/don't-build decisions.

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.

Comprehending and investigating codebases: structure mapping, feature discovery, data flow tracing for 'does X exist?' or 'how does Y work?'. Includes a conversational ask mode. Does not write code.

Takes a high-level feature from an Epic and generates a detailed Product Requirements Document (PRD) in Markdown, covering goals, user stories, requirements, and acceptance criteria.

Stress-test a feature idea for an existing product by surfacing risky assumptions across Value, Usability, Viability, and Feasibility using multi-perspective devil's advocate thinking.

Build empowered product teams that own continuous discovery and delivery, shifting from feature factories to outcome-driven innovation.

Generates feature ideas from PM, Designer, and Engineer perspectives for initial product discovery of a new product.

Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.

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

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'.

Create OR review a page-brief — the artifact BETWEEN a wireflow and the full PRD. It turns each unique page/screen of a product into documented requirements TIED TO JOBS: a self-contained board card per page (what the page is accountable for, the job-tagged checklist of what it must let you do, the journeys it appears in, what it connects to, and the acceptance criteria that say how you'd know it's right). It is the "PRD per page", not a sitemap — and it stops ABOVE the screen: no components, no layout, no hierarchy. Use whenever the user wants to "spec the pages", "document each screen", turn a wireflow + live design into per-page requirements, or asks "what does this page need to do / which jobs pass through it" — even if they never say "page-brief". Natural NEXT STEP after the wireflow skill. ALSO use it to REVIEW an existing page-brief / screen catalog. In the A-Team pipeline this is a definition-phase skill: output lands in docs/features/<slug>/briefs/pages/, job codes are the durable [[NN]] ids from doc