product-capability

Convert product intent and roadmap discussions into ECC-native capability contracts.

Updated Apr 25, 2026

Search Tags:#requirements #roadmap #prd #translate #capability-contract #ecc-native

Ready to run

npx skills add https://github.com/ldk-hub/broke-shopping --skill product-capability-ldk-hub

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-capability
Source: https://github.com/ldk-hub/broke-shopping/tree/main/.agent/.agents/skills/product-capability
Command: npx skills add https://github.com/ldk-hub/broke-shopping --skill product-capability-ldk-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate ambiguous PRD intent, roadmap asks, or product discussions into a clear, implementation-ready capability contract that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts.

Core Features & Use Cases

Restate capability: compress the ask into a precise capability statement describing who benefits, what changes, and the expected outcome.
Resolve constraints: extract business rules, scope boundaries, invariants, trust boundaries, data ownership, and migration needs.
Define implementation contract: generate an SRS-style plan with capability summary, actors, surfaces, states/transitions, interfaces, data models, and governance constraints.
Reusable handoff: produce artifacts suitable for downstream ECC lanes and future re-use across harnesses.

Quick Start

Provide an ECC-native capability plan from a PRD or roadmap item that captures constraints, interfaces, and open questions as a ready-to-implement artifact.

Frequently Asked Questions about product-capability

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

FAQPage Schema

How do I translate a PRD into engineering constraints for multi-service work?▼

A capability contract exposes business rules, invariants, scope boundaries, trust boundaries, data ownership, and migration needs upfront. It also defines actors, surfaces, states, interfaces, and governance constraints to prevent ambiguity before multi-service work starts.

How do I generate a capability contract from roadmap items or founder notes?▼

Generating a capability contract from roadmap items involves restating the ask into a precise capability summary, resolving constraints, and defining implementation interfaces and data models. This produces a ready-to-implement artifact for downstream engineering lanes.

Can I use a capability contract to clarify open decisions across multiple repos?▼

Yes, you can use a capability contract to clarify open decisions across multiple repos by explicitly capturing unresolved questions and trust boundaries. It generates a durable artifact ensuring all downstream services share the same constraints and governance logic.

What is the best way to document data implications and interfaces before implementation?▼

The best way to document data implications and interfaces is to generate an SRS-style capability plan covering data models, state transitions, and surface interfaces. This durable artifact captures governance constraints and open questions for future reuse across harnesses.

Does this approach work for structuring product intent without existing dependencies?▼

Yes, this approach works without external dependencies by taking raw PRDs, roadmap asks, or founder notes as input. It processes the ambiguous product intent directly to output a structured capability contract clarifying invariants and migration needs.