031-architecture-adr-functional-requirements
帮助团队明确接口与命令行设计决策并形成可追溯记录。
交互式发现并为 CLI 或 REST API 的功能性需求生成 ADR 文档。
通过引导式对话把命令行或 HTTP 服务的功能需求梳理清楚，并生成 ADR（Architectural Decision Record）文档。适合在需要记录 CLI 或 REST/HTTP API 的接口设计和功能决策时使用。特别之处是交互式提问能帮你边聊边提炼出明确的决策点，会根据上下文判断是 CLI 还是 API，并产出可直接存档的 ADR。
▸ 展开 SKILL.md 英文原文
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. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR; Decide CLI versus REST functional requirements for an ADR. Part of Plinth Toolkit
帮我安装这个 skill：https://raw.githubusercontent.com/jabrena/plinth/main/skills/031-architecture-adr-functional-requirements/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/jabrena/plinth/main/skills/031-architecture-adr-functional-requirements/SKILL.md"# 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 the current workspace when possible; ask a short clarifying question when unclear. Use only the current conversation and repository files explicitly available in the current session. **What is covered in this Skill?** - Surface discovery: CLI, REST/HTTP API, or both (inference + confirmation) - Initial contex