031-architecture-adr-functional-requirements
This Claude Code skill guides users through structured conversational discovery to create Architectural Decision Records documenting functional requirements and technical decisions for command-line tools, REST/HTTP APIs, or both. Use it when you need to capture and formalize architectural decisions, define functional requirements with stakeholder input, or document the design rationale for CLI or API projects through iterative questioning.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/031-architecture-adr-functional-requirements && cp -r /tmp/031-architecture-adr-functional-requirements/skills/031-architecture-adr-functional-requirements ~/.claude/skills/031-architecture-adr-functional-requirementsSKILL.md
# Create ADRs for Functional Requirements (CLI and/or REST API) Guide stakeholders through a structured conversation to uncover and document technical decisions and functional requirements for command-line tools, REST/HTTP APIs, or combined surfaces. **This is an interactive SKILL**. The ADR is the documentation of that conversation, not the conversation itself. Infer CLI vs API from project context when possible; ask a short clarifying question when unclear. **What is covered in this Skill?** - Surface discovery: CLI, REST/HTTP API, or both (inference + confirmation) - Initial context: purpose, users/consumers, constraints, timeline, load (API when relevant) - Functional requirements: surface-specific workflows, I/O, resources, errors - Technical decisions: language/framework; REST blocks (API design, auth, data, infra, testing/monitoring) and/or CLI blocks (architecture, data/integration, testing/distribution) - Decision synthesis and validation before ADR creation - ADR document generation and next steps ## Constraints Use conversational discovery—ask 1-2 questions at a time, build on answers, validate before proceeding. Only create ADR after thorough conversation and user confirmation. - **MANDATORY**: Run `date` before starting to get accurate timestamps for the ADR - **MUST**: Read the reference template fresh—do not use cached questions - **MUST**: Ask one or two questions at a time; never all at once - **MUST**: Validate summary with user (Does this accurately capture your requirements?) before proposing ADR creation - **MUST**: Wait for user to confirm proceed before generating the ADR ## When to use this skill - Create ADR for functional requirements - Document functional requirements - Capture functional requirements - Generate functional requirements in an ADR ## Workflow 0. **Get current date** Run `date` before discovery and use it for ADR timestamps. 1. **Read reference and discover surface scope** Read `references/031-architecture-adr-functional-requirements.md`, infer CLI/API scope from project context, and ask a short clarifying question if unclear. 2. **Run conversational discovery** Ask one or two questions at a time to capture context, functional requirements, and technical decisions for CLI, REST API, or both. Step constraints: - Never ask all discovery questions at once - Validate summary with user before proposing ADR generation 3. **Generate ADR after explicit confirmation** Only after user confirms proceed, generate the ADR document and provide concise next steps. ## Reference For detailed guidance, examples, and constraints, see [references/031-architecture-adr-functional-requirements.md](references/031-architecture-adr-functional-requirements.md).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
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. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project