ワンクリックでManusで任意のスキルを実行

$pwd:

031-architecture-adr-functional-requirements

Name: 031 Architecture Adr Functional Requirements
Author: jabrena

// 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

Manusで実行

$ git log --oneline --stat

stars:0

forks:2

updated:2026年3月19日 20:26

ファイルエクスプローラー

2 ファイル

SKILL.md

readonly

name	031-architecture-adr-functional-requirements
description	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
license	Apache-2.0
metadata	{"author":"Juan Antonio Breña Moral","version":"0.13.0-SNAPSHOT"}

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.

related-skills.json

同じリポジトリ

014-agile-create-user-story.md

from "jabrena/cursor-rules-examples"

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. Part of the skills-for-java project

2026-03-190

020-planning-enhance-ai-plan-mode.md

from "jabrena/cursor-rules-examples"

Use when creating a plan using Plan model and enhancing structured design plans in Cursor Plan mode for Java implementations. Use when the user wants to create a plan, design an implementation, structure a development plan, or use plan mode for outside-in TDD, feature implementation, or refactoring work. Part of the skills-for-java project

2026-03-190

030-architecture-adr-general.md

from "jabrena/cursor-rules-examples"

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. Part of the skills-for-java project

2026-03-190

032-architecture-adr-non-functional-requirements.md

from "jabrena/cursor-rules-examples"

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

2026-03-190

033-architecture-diagrams.md

from "jabrena/cursor-rules-examples"

Use when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, and ER (Entity Relationship) diagrams — through a modular, step-based interactive process that adapts to your specific visualization needs. Part of the skills-for-java project

2026-03-190

110-java-maven-best-practices.md

from "jabrena/cursor-rules-examples"

Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. Part of the skills-for-java project

2026-03-190

package.json

"author": "jabrena"

"repository": "jabrena/cursor-rules-examples"

GitHub リポジトリを開く Creator のリポジトリを見る

$ install --global

$ download --local

Manusで実行

$ useful --forSOC

ソフトウェア開発者コンピュータ・数学職15-1252L4

name	031-architecture-adr-functional-requirements
description	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
license	Apache-2.0
metadata	{"author":"Juan Antonio Breña Moral","version":"0.13.0-SNAPSHOT"}

Create ADRs for Functional Requirements (CLI and/or REST API)

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.

031-architecture-adr-functional-requirements

Create ADRs for Functional Requirements (CLI and/or REST API)

Constraints

When to use this skill

Reference

このリポジトリの他の Skills

このリポジトリの他の Skills

Create ADRs for Functional Requirements (CLI and/or REST API)

Constraints

When to use this skill

Reference