product-capability

Translate product intent into explicit capability contracts with constraints and interfaces.

86|21|Updated Feb 9, 2026

Search Tags:#architecture #handoff #stakeholders #product-requirements #design-criteria #capability-contract

Ready to run

npx skills add https://github.com/Jamkris/everything-gemini-code --skill product-capability-jamkris

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-capability
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/product-capability
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill product-capability-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate product intent into explicit engineering constraints, ensuring a durable, reusable artifact before coding.

Core Features & Use Cases

Provide a durable capability artifact that captures constraints, interfaces, and unresolved decisions.
Align multiple teams and services around a single capability contract to reduce rework.
Enable reuse of the capability artifact across harnesses and sessions.

Quick Start

Convert a PRD, roadmap item, or founder note into a concrete capability contract that clearly defines constraints, interfaces, and unresolved decisions.

Frequently Asked Questions about product-capability

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

FAQPage Schema

How do I translate product intent into engineering constraints before coding?▼

To translate product intent into engineering constraints, you convert a PRD or roadmap item into an explicit capability contract that exposes invariants, interfaces, and unresolved decisions, creating a durable artifact to prevent misalignment and rework before coding begins.

What is a capability contract and when do I need one for my product?▼

A capability contract is a durable artifact that captures constraints, interfaces, and unresolved decisions from product intent. You need one when product context spans multiple services or teams and an early, durable artifact is required to enforce non-negotiable rules, ownership, and clear handoffs.

How do I align multiple teams and services around product requirements to reduce rework?▼

To align multiple teams and services around product requirements, you generate a ready-to-implement SRS-style plan that enforces lifecycle transitions and ownership, ensuring all stakeholders operate from a single, reusable capability contract to reduce rework.

Can I use founder notes or forum discussions to create a ready-to-implement SRS-style plan?▼

Yes, you can use founder notes or forum discussions to create a ready-to-implement SRS-style plan. The process translates these unstructured product intents into an explicit capability contract that defines constraints, interfaces, and unresolved decisions for implementation.

Does this approach work for capturing design criteria and lifecycle transitions across services?▼

Yes, this approach works for capturing design criteria and lifecycle transitions across services. It translates product intent into an explicit contract that enforces non-negotiable rules, ownership, and clear handoffs, producing a durable artifact that spans multiple teams.

When should I not use a capability contract for stakeholder handoffs?▼

You should avoid using a capability contract for stakeholder handoffs if your product context does not span multiple services or teams. If an early, durable artifact is unnecessary for preventing misalignment, applying this formal contract enforcement may introduce unnecessary overhead.