What problem does it solve? Large features often get planned on implicit assumptions that only surface mid-implementation or in review. This Skill sits between a captured request and the implementation plan, classifying the cycle's size and, for Large cycles, making constraints explicit — invariants, trust boundaries, data ownership, lifecycle transitions, and cross-service interfaces — before any code is planned. ## Core Features & Use Cases - Size classification: Reads request.md, the canonical spec, and affected code to classify a cycle as Small, Medium, or Large, recording the result so downstream phases do not re-derive it. Small and Medium cycles exit immediately with a four-line capability.md. - Constraint resolution for Large cycles: Produces capability.md covering invariants, trust boundaries, data ownership, state transitions, interfaces, policy, rollout, and failure handling, with each statement marked as fixed policy, architecture preference, or open question. - Explicit handoff decision: Ends with exactly one of three handoffs — ready to refine, needs architecture review, or needs product decision — and never reports ready while a blocking question is open. - Use Case: A request to build a patient episode timeline spans three modules and publishes a new endpoint consumed by a mobile app. The Skill classifies it Large, records the invariant that episodes never leak across clinics (enforced server-side), flags a conflict with the existing immutability spec as blocking, and hands off for a product decision. ## Quick Start Ask the assistant to map the capability for the current cycle, for example by saying "mapeia a capacidade" after a request.md exists but before any plan.md is written.
