product-capability

Transform product requirements into engineering specifications with Laravel architectural constraints.

Updated Jan 6, 2023

Search Tags:#architecture #documentation #requirements #laravel #product-management #engineering-planning

Ready to run

npx skills add https://github.com/pekral/phpstan-rules --skill product-capability-pekral

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-capability
Source: https://github.com/pekral/phpstan-rules/tree/main/.claude/skills/product-capability
Command: npx skills add https://github.com/pekral/phpstan-rules --skill product-capability-pekral

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill bridges the gap between high-level product requirements and technical implementation by forcing the explicit definition of architectural constraints, interfaces, and open questions before any code is written.

Core Features & Use Cases

Constraint Extraction: Systematically identifies business rules, invariants, and trust boundaries.
Contract Definition: Standardizes the definition of actors, surfaces, states, and data models to ensure alignment with existing architecture.
Use Case: When a new feature request is ambiguous, use this Skill to generate a structured PRODUCT.md file that clarifies exactly what must be true for the engineering team to begin development.

Quick Start

Use the product-capability skill to analyze the current PRD for the new user authentication flow and generate an implementation plan.

Frequently Asked Questions about product-capability

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

FAQPage Schema

How do I turn vague product requirements into engineering specifications?▼

To turn vague product requirements into engineering specifications, you extract business rules, invariants, and trust boundaries to define architectural constraints, actors, and data models. This generates a structured PRODUCT.md file clarifying exact implementation contracts before coding begins.

How do I document open product decisions for a complex feature spanning multiple system surfaces?▼

To document open product decisions for complex features spanning multiple system surfaces, you explicitly define architectural constraints and interfaces. This systematically records all unresolved product decisions alongside implementation contracts to ensure engineering alignment.

Can I use this approach to generate engineering plans for Laravel-based applications?▼

Yes, generating engineering plans for Laravel-based applications requires strict adherence to existing Laravel architectural patterns. It standardizes the definition of actors, surfaces, states, and data models to ensure new feature alignment with your current architecture.

What is the best way to bridge the gap between high-level PRDs and technical implementation?▼

Bridging the gap between high-level PRDs and technical implementation is best achieved by forcing the explicit definition of architectural interfaces and open questions. This systematically identifies business rules and trust boundaries to generate concrete engineering specifications.

Do I need a complete PRD to start defining architectural constraints and contracts?▼

You do not need a complete PRD to start defining architectural constraints and contracts. The process analyzes ambiguous feature requests to systematically extract invariants, standardize interfaces, and explicitly document unresolved product decisions.