extract-constraints

What problem does it solve?

Technical constraints from the ecosystem (APIs, compliance, platform) are often implicit, leading to design flaws or non-compliance if not explicitly documented.

Core Features & Use Cases

• Constraint Extraction: Identifies and documents technical constraints (C-*) from external APIs, compliance regulations, and platform dependencies.
• Ecosystem Acknowledgment: Clearly distinguishes between given constraints and chosen design decisions, providing clarity.
• Design Context: Provides crucial context for architectural decisions and enables constraint-aware code generation.
• Use Case: When defining requirements for a payment feature, use this skill to extract constraints like "Stripe API timeout: 10 seconds" (C-001) or "PCI-DSS Level 1 compliance" (C-020), ensuring they are explicitly acknowledged.

Quick Start

Extract technical constraints (C-*) from the 'User Login' requirement, focusing on API timeouts and password hashing standards.