Results for “features”

Conduct a structured competitive analysis comparing UX patterns, features, strengths, and gaps across rival products.

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

Update an existing implementation plan file with new or updated requirements for features, refactoring, package upgrades, design, architecture, or infrastructure.

Design the structure, hierarchy, and navigation model for a product's content and features.

Review designs, products, and features using Steve Jobs' standards of ruthless simplicity, focus, and end-to-end excellence.

Researches competitors, compares features, pricing, and tech stacks, then produces a prioritized gap analysis with actionable roadmap.

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

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

Craft clear, empathetic end-of-life announcements for products, features, or plans, including rationale, customer impact, and transition support.

Narrates a demo video for Loki Mode, a multi-agent autonomous startup system for Claude Code, covering setup, phases, and features.

Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.

Generate comprehensive Product Requirements Documents (PRDs) for software systems and AI-powered features, including executive summaries, user stories, technical specifications, and risk analysis.

Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.

Visualize the user journey by creating a hierarchical map of activities, steps, and tasks to build shared understanding and prioritize features.

Generates a structured 6-minute two-person English product presentation script, split into unique features/target customers and market comparison/competitive advantages, with time allocations and full dialogue.

Analyzes an app from video, screenshots, or URL and produces a structured product breakdown covering features, UX, monetization, market, and recommendations.

This skill should be used when implementing features from a PRD spec, tracking implementation progress, or resuming work across sessions. Covers Dex task management for PRD story execution, daily workflows, and skill auto-loading.

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.

Behavior-driven development: Discovery → Formulation → Automation. Use when the user wants to build features or fix bugs via Gherkin scenarios and the BDD lifecycle, or mentions BDD/Gherkin/Executable Specifications. Delegates test implementation to /mattpocock:tdd.

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.

Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.

Converts existing PRDs into the prd.json format used by the Ralph autonomous agent system, including splitting large features into right-sized stories and creating a progress file.

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

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

Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Use for Jira project setup, configuration, advanced search, dashboard creation, workflow design, and technical Jira operations.

Threat modeling workflow for software systems: scope, data flow diagrams, STRIDE analysis, risk scoring, and turning mitigations into backlog and tests. Use when designing new features, reviewing architecture changes, handling sensitive data, or hardening auth/payment/multi-tenant flows.

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.

Turns vague features, bug clusters, roadmap items, or launch work into an execution-ready planning packet by choosing the right packet type, separating discovery from delivery, and making blockers, dependencies, and the next move explicit.

Architecture discovery for Sage/Acorn projects — map existing codebase, discover post types, routes, ACF field groups, Livewire components, Service Providers, identify architectural gaps, architecture decision records, ADR, component boundary map, data flow diagram, risk register, implementation sequencing, discovery session, understanding unknown codebases, use before architecting or building new features, output contract, discover-abilities

Creates decision-focused PRDs and product specs — the kind that make explicit decisions, not document hopes. Make sure to use this skill whenever someone asks to write, review, draft, or improve any product document, including PRDs, feature specs, requirements docs, or product specifications. Trigger even when the user doesn't say "PRD" explicitly — phrases like "write a spec for X", "define requirements for Y", "what should my PRD include", "help me document this feature", or "my spec feels too vague" all apply. Do not attempt to write the PRD directly without consulting this skill. Produces 5-stage PRDs with behavior contracts (15-25 labeled examples for AI features), measurable success metrics with specific thresholds, precise rollout plans with percentages and ramp gates, and antipattern detection. Works for AI features, SaaS, mobile apps, and traditional software.