Generate and modify source code to satisfy dx declaration specifications.
npx skills add https://github.com/dewitt/dx --skill implementer-dewitt
Please help me install this Agent Skill. Skill: implementer Source: https://github.com/dewitt/dx/tree/main/skills/implementer Command: npx skills add https://github.com/dewitt/dx --skill implementer-dewitt
This skill bridges the gap between high-level architectural specifications and concrete, functional code, ensuring that implementations strictly adhere to defined invariants and contracts.
Ask the implementer to generate the source code for the system described in the system.md declaration file.
High-intent search queries and answers about installing and using this skill.
To generate source code from a specification file, you need a dx declaration file defining your architectural invariants and contracts. The implementer skill reads these declarations and automatically generates or modifies imperative source code to satisfy the specified black-box contracts.
Spec-driven code generation enforces architectural contracts by using the dx toolchain to lint specifications and verify contract conformance. It ensures every generated line of imperative source code strictly adheres to the invariants and black-box contracts defined in your declaration files.
To manage design assumptions when a specification is silent, you should use a structured assumption management workflow. This involves logging and tracking design decisions made during the implementation lifecycle to maintain a record of deviations from the original architectural specifications.
Yes, you need the dx toolchain to verify contract conformance during the implementation lifecycle. The toolchain is required to lint your dx declaration specifications and ensure that the generated code continuously satisfies the defined architectural invariants and contracts.
Yes, you can update existing imperative source code to match new architectural specifications. The implementer modifies current codebases to strictly adhere to updated dx declarations, ensuring that any changes to black-box contracts and invariants are accurately reflected in the implementation.
Spec-driven implementation bridges the gap between high-level architectural specifications and functional code. It ensures strict adherence to defined invariants and contracts, preventing manual coding errors and maintaining continuous contract verification throughout the software development lifecycle.
dewittDistill imperative source code into a declarative dx specification.
dewittEnforce a specification-first workflow with role-based transitions in dx-managed repositories.
fsollaFacilitate assumption mapping workshops to validate design hypotheses with outcome-based metrics.
dewittVerify software implementations against dx declaration contracts via black-box testing.
