How do I install the 031 Architecture Adr Functional Requirements skill?

Run npx skillmds@latest add jabrena/031-architecture-adr-functional-requirements in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is 031 Architecture Adr Functional Requirements safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 031 Architecture Adr Functional Requirements?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 031 Architecture Adr Functional Requirements free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published 031 Architecture Adr Functional Requirements?

jabrena (@jabrena) published this skill. Their other Agent Skills are listed on their SkillMD profile.

031 Architecture Adr Functional Requirements by jabrena

Name: 031 Architecture Adr Functional Requirements
Author: jabrena

031 Architecture Adr Functional Requirements

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. Part of the skills-for-java project

jabrena Updated Sep 17, 2026

File contents

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

Document CLI or REST architecture
Create ADR for functional requirements
ADR for command-line tool or HTTP API
Functional requirements ADR

Reference

For detailed guidance, examples, and constraints, see references/031-architecture-adr-functional-requirements.md.

---name: 031-architecture-adr-functional-requirementsdescription: Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. Part of the skills-for-java projectlicense: Apache-2.0---# 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## ConstraintsUse 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- Document CLI or REST architecture- Create ADR for functional requirements- ADR for command-line tool or HTTP API- Functional requirements ADR## ReferenceFor detailed guidance, examples, and constraints, see [references/031-architecture-adr-functional-requirements.md](references/031-architecture-adr-functional-requirements.md).

Frequently asked questions