OpenParable
Skip to content
← Back to skills

031 Architecture Adr Functional Requirements CLI

Documents
031-architecture-adr-functional-requirements-cli

031 Architecture Adr Functional Requirements CLI is an Agent Skill for documents published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/development/031-architecture-adr-functional-requirements-cli/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/031-architecture-adr-functional-requirements-cli, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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