product-capability

Translate PRDs and roadmap items into structured SRS-style capability plans.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/luongldptit/move-ticket --skill product-capability-luongldptit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-capability
Source: https://github.com/luongldptit/move-ticket/tree/main/.agent/.agents/skills/product-capability
Command: npx skills add https://github.com/luongldptit/move-ticket --skill product-capability-luongldptit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the gap between clear product intent and actionable engineering implementation by surfacing hidden constraints, assumptions, and unresolved decisions that typically cause rework and misalignment during cross-team feature development.

Core Features & Use Cases

  • Capability Plan Generation: Translates PRDs, roadmap items, product discussions, or founder notes into structured SRS-style capability plans with explicit constraints, invariants, and interface definitions.
  • Cross-Team Alignment: Creates durable, reusable artifacts that survive across sessions and AI coding harnesses, eliminating the need to repeatedly restate hidden assumptions during engineering reviews.
  • Use Case: For a cross-service payment feature where product requirements are clear but architecture, data ownership, compliance, and rollout implications are still fuzzy, this Skill produces a complete capability contract ready for implementation.

Quick Start

Use the product-capability skill to convert your PRD for the new user referral program into a detailed implementation-ready plan with all constraints, non-goals, and open questions clearly listed for the engineering team.

Frequently Asked Questions about product-capability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a PRD into an implementation-ready plan for engineering?

To convert a PRD into an implementation-ready plan, translate product intent into structured SRS-style capability plans. This surfaces hidden constraints, defines state transitions, and lists open questions to eliminate engineering rework.

What is a capability contract and when do I need one for cross-service features?

A capability contract is a structured artifact defining architecture, data lifecycle, and security implications. You need one for cross-service features when product requirements are clear but implementation constraints remain undefined.

How do I surface hidden assumptions and constraints before coding begins?

Surface hidden assumptions by generating SRS-style artifacts from product discussions. This process explicitly defines non-goals, invariants, and interface definitions to resolve unresolved decisions before coding begins.

Can I use this to create implementation plans for cross-team feature development?

Yes, you can create implementation plans for cross-team feature development. It produces durable capability summaries and open question lists that ensure consistent execution and alignment across teams and AI coding harnesses.

Does this work with roadmap items and founder notes or only formal product requirements?

Yes, it works with roadmap items and founder notes. It translates implicit product intent from various sources into explicit, implementation-ready capability plans with clearly listed constraints and non-goals.

What is the best way to align engineering teams on complex product requirements?

The best way to align engineering teams is to generate durable capability contracts from product requirements. These artifacts survive across sessions, capturing state transitions and interface definitions to prevent misalignment.