Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jabrena/031-architecture-adr-functional-requirements
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both.
Passed 6 of 14 test cases with the skill, and 2 of 14 without it.
and 7 more in the full report
9 fixed1 passed either way10 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to document the functional requirements and architectural choices for a new command-line developer utility we are building. Please guide me step-by-step through the design questions, summarize our choices for my review, and then produce the final ADR document.
| Checked | Without skill | With skill |
|---|---|---|
| The response poses at most two questions in its first response. | Missed | Passed |
| The response asks questions focusing on the command-line surface or tool scope before drafting the final document. | Passed | Passed |
The instructions your model reads when the skill loads.
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?
Use conversational discovery in small batches, build on answers, validate before proceeding. Only create ADR after thorough conversation and user confirmation.
date command before starting to get accurate timestamps for the ADRUse the local shell date command before discovery and use it for ADR timestamps.
Load references/031-architecture-adr-functional-requirements.md from this skill, infer CLI/API scope from the current workspace, and ask a short clarifying question if unclear.
test cases passed, vs 2 / 14 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.