Results for “feature-development”

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.

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

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

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.

Build empowered product teams using discovery and delivery dual-track. Use when the user mentions "product discovery", "empowered teams", "feature factory", "product roadmap", "opportunity assessment", "product vision", "product-led growth", or "discovery vs delivery". Also trigger when restructuring product teams away from output-driven models, setting product strategy, or defining what to build next based on outcomes. Covers product discovery techniques, team structure, and continuous value delivery. For customer interviews, see mom-test. For ongoing discovery systems, see continuous-discovery.

Use when driving a feature prompt to a production-ready PR through discovery, definition, design, spec, issues, and dev phases, or when the user runs /feature or /feature resume — orchestrates the A-Team agentic pipeline over a target repo.

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

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

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

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.

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.

PIV workflow orchestrator - Plan, Implement, Validate loop for systematic multi-phase software development. Use when building features phase-by-phase with PRPs, automated validation loops, or multi-agent orchestration. Supports PRD creation, PRP generation, codebase analysis, and iterative execution with validation.

Creates concise early UX discovery artifacts for PRD development, customer development, new product ideas, feature bets, and redesigns. Use when the user asks to hypothesize an ideal customer profile, generate proto-personas, write customer problem or jobs-to-be-done hypotheses, create journey maps, shape value propositions, or turn product context into design-sprint-style customer insight artifacts for product and engineering teams.