Loading...
Loading...
Found 30 Skills
Documents a strategic pivot or persevere decision with the evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market feedback.
Framework for structured product decision-making. Use when facing complex tradeoffs, aligning stakeholders, documenting decisions, or choosing between multiple valid approaches.
Document architectural decisions. Use when making significant technical decisions that should be recorded. Covers ADR format and decision documentation.
Document finalized technology selections, architecture decisions, long-term constraints, and coding conventions in the project into searchable permanent documents. No one will remember why X was chosen six months later, but with decision documents, at least the background can be understood before making changes next time. Four types: tech-stack (which tools/libraries/frameworks to use), architecture (how the system is organized), constraint (what is not allowed), convention (what is uniformly done). Trigger scenarios: Proactively push when important choices are made after feature-design or issue-analyze, or when the user says "record decision", "archive technology selection", "ADR", "record this constraint", "write down the convention". Only archive finalized decisions; do not archive under-discussion solutions.
Create comprehensive implementation plans and write them to plan files. Use when the user asks for a plan, comprehensive plan, systematic workflow design, or wants decisions documented in a plan file.
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. Part of the skills-for-java project