How do I install the 032 Architecture Adr Functional Requirements REST skill?

Run npx skillmds add majiayu000/032-architecture-adr-functional-requirements-rest 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 032 Architecture Adr Functional Requirements REST safe to use?

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

Which AI agents work with 032 Architecture Adr Functional Requirements REST?

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.

Who published 032 Architecture Adr Functional Requirements REST?

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

032 Architecture Adr Functional Requirements REST by majiayu000

Name: 032 Architecture Adr Functional Requirements REST
Rating: 4.5 (4 reviews)
Author: majiayu000

032 Architecture Adr Functional Requirements REST

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

majiayu000 0637aff 2 files · 2.9 KB Updated Sep 9, 2026 567 repo stars

File contents

Create ADRs for REST API Development

Guide stakeholders through a structured conversation to uncover and document technical decisions and functional requirements for REST API implementations. This is an interactive SKILL. The ADR is the documentation of that conversation, not the conversation itself.

What is covered in this Skill?

Initial context: API purpose, consumers, constraints, load
Functional requirements: use cases, resources, operations, response formats, error handling
Technical decisions: language/framework, API design, auth/security, data, integration, infrastructure, testing, monitoring
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

Reference

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

---name: 032-architecture-adr-functional-requirements-restdescription: Facilitates conversational discovery to create Architectural Decision Records (ADRs) for REST API development. Use when the user wants to document REST API architecture, capture functional requirements for APIs, create ADRs for REST/HTTP services, or design APIs with documented decisions. Part of the skills-for-java projectlicense: Apache-2.0---# Create ADRs for REST API Development Guide stakeholders through a structured conversation to uncover and document technical decisions and functional requirements for REST API implementations. **This is an interactive SKILL**. The ADR is the documentation of that conversation, not the conversation itself. **What is covered in this Skill?** - Initial context: API purpose, consumers, constraints, load - Functional requirements: use cases, resources, operations, response formats, error handling - Technical decisions: language/framework, API design, auth/security, data, integration, infrastructure, testing, monitoring - 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 ## Reference For detailed guidance, examples, and constraints, see [references/032-architecture-adr-functional-requirements-rest.md](references/032-architecture-adr-functional-requirements-rest.md).

Frequently asked questions