Richard Carson Derr
Community@Zaba505 · Raleigh, NC, USA
Go priest, Java practitioner, and tinkerer in everything else
Agent Skills by Richard Carson Derr
Showing 9 vetted skills indexed across 1 GitHub repositories.
Zaba505plan-adrs
Enumerates architectural decisions from technical requirements and files one GitHub issue per ADR.
Zaba505extract-business-requirements
Extracts sourced business requirements from capability and user experience docs into a living markdown document.
Zaba505plan-implementation
Breaks a completed capability tech design into implementation tasks and files one GitHub issue per task.
Zaba505define-capability
Guides conversational elicitation of business capabilities into structured markdown documents.
Zaba505plan-experiences
Enumerates user experiences for a capability and files one GitHub issue per experience.
Zaba505define-adr
Drafts a single capability-scoped Architecture Decision Record in MADR 4.0.0 format.
Zaba505plan-tech-design
Compose skeleton tech-design documents from accepted ADRs and file GitHub issues per component and gap.
Zaba505define-user-experience
Guides definition of a user experience journey documented under an existing business capability.
Zaba505define-technical-requirements
Extracts technical requirements from reviewed business requirements into a living tech-requirements.md document.
Frequently Asked Questions About Richard Carson Derr
FAQPage SchemaWhat tasks can I accomplish with Zaba505's skills?▼
You can define business capabilities, extract business and technical requirements documents, plan and author Architecture Decision Records, compose tech-design documents with component inventories, define user experiences, and file GitHub issues for ADRs, components, and implementation tasks.
Who are these skills designed for?▼
Software architects, technical leads, and engineers practicing capability-driven design. They suit teams that want traceability from business requirements (BR-NN) through technical requirements (TR-NN) to ADRs, component designs, and implementation tasks before writing code.
How do the skills work together in practice?▼
They form a strict sequence: define-capability, plan-experiences and define-user-experience, extract-business-requirements, define-technical-requirements, plan-adrs and define-adr, plan-tech-design, then plan-implementation. Each skill refuses out-of-order use and routes you back to the correct prerequisite step.
Do the skills make architectural decisions automatically?▼
No. The define-adr skill identifies research tasks, proposes at least two options tied to TR-NNs, and surfaces trade-offs, but always waits for a human to make the final selection. Planning skills only enumerate decisions and file issues; they never draft the ADRs themselves.
What are the prerequisites for using these skills?▼
Each skill requires upstream artifacts: capabilities before experiences, business-requirements.md before technical requirements, accepted ADRs before tech-design composition, and a complete tech design before implementation planning. GitHub issue filing requires a repository where issues can be created.