Formalize accepted ADRs into implementation specifications with interface boundaries and data structures.
npx skills add https://github.com/oakoss/oakterm --skill write-spec-oakoss
Please help me install this Agent Skill. Skill: write-spec Source: https://github.com/oakoss/oakterm/tree/main/.claude/skills/write-spec Command: npx skills add https://github.com/oakoss/oakterm --skill write-spec-oakoss
This skill bridges the gap between high-level architectural decisions and concrete implementation by formalizing ambiguous requirements into rigorous, testable specifications.
Use the write-spec skill to generate a formal implementation specification based on the accepted ADR-0001 regarding the new plugin architecture.
High-intent search queries and answers about installing and using this skill.
To convert an ADR into a formal implementation specification, you formalize architectural decisions into concrete interface boundaries, data structures, and behavioral constraints. This process validates type definitions and error handling against project templates.
Formalizing ambiguous architectural decisions into testable specs involves defining exact interface boundaries, wire protocols, and data formats. It isolates bounded concerns to ensure modular architecture and uses a checklist to eliminate hand-waving.
Defining interface boundaries and data structures from accepted idea documents requires transforming them into structured documentation. This specifies exact behavioral constraints and validates technical rigor for complex system components.
Yes, this specification approach works for validating type definitions and error handling. It ensures technical rigor by checking these elements against project-specific templates to eliminate hand-waving before coding begins.
You need to formalize architectural decisions into implementation specs when bridging the gap between high-level architecture and concrete implementation. It is required to produce rigorous, testable specifications for complex system components.
zalman0813Automate ADR lifecycle transitions across proposed, accepted, and deprecated states.
Pact-Community-OrganizationDefine and enforce Pact interface signatures across modules.
KrishpotanwarConvert monolithic codebases into modular domain-oriented architecture with bounded contexts.
ConductionNLReverse-engineer formal technical specifications from observed code behavior.
