Agent skill
031-architecture-adr-functional-requirements-cli
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for CLI development. Use when the user wants to document CLI architecture, capture functional requirements for a command-line tool, create ADRs for CLI projects, or design CLI applications with documented decisions. Part of the skills-for-java project
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/031-architecture-adr-functional-requirements-cli
Metadata
Additional technical details for this skill
- author
- Juan Antonio Breña Moral
- version
- 0.13.0-SNAPSHOT
SKILL.md
Create ADRs for CLI Development
Guide stakeholders through a structured conversation to uncover and document technical decisions and functional requirements for CLI applications. 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: CLI purpose, users, constraints, timeline
- Functional requirements: workflows, commands, input/output, UX
- Technical decisions: language/framework, 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
datebefore 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 sound accurate?") before proposing ADR creation
- MUST: Wait for user to confirm "proceed" before generating the ADR
Reference
For detailed guidance, examples, and constraints, see references/031-architecture-adr-functional-requirements-cli.md.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?