{"skill":{"slug":"implementing-architecture","displayName":"Implementing Architecture","summary":"Use when: about to write code and docs/architecture/ exists with STATUS: APPROVED in architecture.yaml. Not when: no approved architecture yet (use compiling...","tags":{"architectural-decision-records":"1.0.2","architecture-as-code-tools":"1.0.2","architecture-constraints-enforcement":"1.0.2","brownfield-refactoring":"1.0.2","deterministic-execution":"1.0.2","developer-tools":"1.0.2","latest":"1.0.2","nfr-enforcement":"1.0.2","prototype-refactoring":"1.0.2","software-architecture-patterns":"1.0.2"},"stats":{"comments":0,"downloads":148,"installsAllTime":0,"installsCurrent":0,"stars":0,"versions":3},"createdAt":1775852518437,"updatedAt":1776194210064},"latestVersion":{"version":"1.0.2","createdAt":1776193519128,"changelog":"implementing-architecture 1.0.2\n\n- Clarified usage for brownfield scenarios: this skill now explicitly applies when refactoring existing prototypes/codebases to conform to an approved architecture (not just greenfield implementation).\n- Added \"Brownfield rule\": made clear that existing code is not architectural authority; implementation means bringing code into compliance, not treating prototypes as source of truth.\n- Expanded \"When NOT to Use\" with rules for handling prototypes and what to do if architecture changes are needed.\n- No behavioral or technical changes—documentation/business process clarification only.","license":"MIT-0"},"metadata":{"os":null,"systems":null},"owner":{"handle":"inetgas","userId":"s17bhed34swjadqd1zh9gjem4x84jxvj","displayName":"inetgas","image":"https://avatars.githubusercontent.com/u/271354125?v=4"},"moderation":null}