[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D73SPNSDSV17F1ZKT9B9VR":3,"skill-same:01M7D73SPNSDSV17F1ZKT9B9VR":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7D73SPNSDSV17F1ZKT9B9VR","architecture-spine",null,"Create, update, or validate a lean architecture spine containing the cross-unit invariants that independently built parts must share. Use before backlog decomposition for multi-epic, cross-system, high-risk, or otherwise coordination-heavy work; not for Task-level code sketches.","Monolith-INC\u002Fmonolithic-dev-harness","Monolith-INC","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235230192?v=4","01M75C94857P7W1N13N4K4E016","Monolith INC","01M7D737W93VBSP0P111E1AJ7M",1,"MIT","https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Farchitecture-spine\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: architecture-spine\ndescription: Create, update, or validate a lean architecture spine containing the cross-unit invariants that independently built parts must share. Use before backlog decomposition for multi-epic, cross-system, high-risk, or otherwise coordination-heavy work; not for Task-level code sketches.\nlicense: MIT\n---\n\n# Architecture Spine\n\nProduce a consistency contract, not an exhaustive solution document. Read\n[`..\u002F..\u002Freferences\u002Fplanning-artifacts.md`](..\u002F..\u002Freferences\u002Fplanning-artifacts.md) first.\nWhen creating or re-rendering the spine, read\n[`references\u002Fspine-template.md`](references\u002Fspine-template.md).\n\nThe inclusion test is strict: if two units one level down built this independently, could they\nchoose incompatibly? Record the decision only when the answer is yes, the choice is non-obvious,\nand a real trade-off exists. Otherwise defer it or let compliant code own it.\n\n## Scope and altitude\n\nSet the scope and altitude from the input:\n\n- initiative spine keeps Features coherent;\n- Feature spine keeps Epics coherent;\n- Epic spine keeps Stories coherent.\n\nA child spine inherits the parent's decisions as read-only constraints. A conflict is surfaced to\nthe parent; never weakened locally. For brownfield work, inspect the actual repository and adopt\nexisting conventions rather than designing a parallel system.\n\n## Coach the load-bearing calls\n\nDefault to coaching unless the user asks for speed. Name a coherent design paradigm first, then\nwork through boundaries and dependency direction, state mutation, shared-data ownership,\nintegration contracts, error and security boundaries, deployment\u002Fenvironment invariants, and other\ndimensions that can create cross-unit divergence. Show realistic alternatives and your lean; the\nuser decides. Verify current versions and fit before naming technologies.\n\nRecord decisions and rationale in `architecture\u002F.decision-log.md`. Stable `AD-N` identifiers are\nnever renumbered or reused.\n\n## Output\n\nWrite `architecture\u002FARCHITECTURE-SPINE.md` with:\n\n- scope, altitude, named paradigm, and inherited invariants;\n- one block per decision: `AD-N`, `Binds`, `Prevents`, and enforceable `Rule`;\n- consistency conventions;\n- minimal stack and structural seed, explicitly owned by code after cold start;\n- `CAP-N` → architecture mapping when a product spec exists;\n- diagrams only where they convey dependency or deployment shape; and\n- explicit deferred decisions with the condition that should reopen them.\n\nKeep rationale in the decision log, not the spine. A whole relevant dimension left silent is a gap;\na dimension explicitly deferred is a decision.\n\n## Review and handoff\n\nCheck every `AD-N` has all three fields, inherited IDs resolve, diagrams are valid, technology\nclaims are current, capabilities have a home, and the spine contains no decision that could safely\nbe read from code. Reconcile all load-bearing inputs before finalizing.\n\nOn update, append the new decision and re-render while preserving IDs. Validation is read-only and\noffers an update. `product-spec` adopts the spine as a companion. The later `architect` skill turns\nan approved Story into code shapes within this spine; it does not replace or override it.\n\nAdapted from BMad Method's Architecture Spine workflow (MIT, BMad Code, LLC).\n","# Architecture Spine\n\nProduce a consistency contract, not an exhaustive solution document. Read\n[`..\u002F..\u002Freferences\u002Fplanning-artifacts.md`](..\u002F..\u002Freferences\u002Fplanning-artifacts.md) first.\nWhen creating or re-rendering the spine, read\n[`references\u002Fspine-template.md`](references\u002Fspine-template.md).\n\nThe inclusion test is strict: if two units one level down built this independently, could they\nchoose incompatibly? Record the decision only when the answer is yes, the choice is non-obvious,\nand a real trade-off exists. Otherwise defer it or let compliant code own it.\n\n## Scope and altitude\n\nSet the scope and altitude from the input:\n\n- initiative spine keeps Features coherent;\n- Feature spine keeps Epics coherent;\n- Epic spine keeps Stories coherent.\n\nA child spine inherits the parent's decisions as read-only constraints. A conflict is surfaced to\nthe parent; never weakened locally. For brownfield work, inspect the actual repository and adopt\nexisting conventions rather than designing a parallel system.\n\n## Coach the load-bearing calls\n\nDefault to coaching unless the user asks for speed. Name a coherent design paradigm first, then\nwork through boundaries and dependency direction, state mutation, shared-data ownership,\nintegration contracts, error and security boundaries, deployment\u002Fenvironment invariants, and other\ndimensions that can create cross-unit divergence. Show realistic alternatives and your lean; the\nuser decides. Verify current versions and fit before naming technologies.\n\nRecord decisions and rationale in `architecture\u002F.decision-log.md`. Stable `AD-N` identifiers are\nnever renumbered or reused.\n\n## Output\n\nWrite `architecture\u002FARCHITECTURE-SPINE.md` with:\n\n- scope, altitude, named paradigm, and inherited invariants;\n- one block per decision: `AD-N`, `Binds`, `Prevents`, and enforceable `Rule`;\n- consistency conventions;\n- minimal stack and structural seed, explicitly owned by code after cold start;\n- `CAP-N` → architecture mapping when a product spec exists;\n- diagrams only where they convey dependency or deployment shape; and\n- explicit deferred decisions with the condition that should reopen them.\n\nKeep rationale in the decision log, not the spine. A whole relevant dimension left silent is a gap;\na dimension explicitly deferred is a decision.\n\n## Review and handoff\n\nCheck every `AD-N` has all three fields, inherited IDs resolve, diagrams are valid, technology\nclaims are current, capabilities have a home, and the spine contains no decision that could safely\nbe read from code. Reconcile all load-bearing inputs before finalizing.\n\nOn update, append the new decision and re-render while preserving IDs. Validation is read-only and\noffers an update. `product-spec` adopts the spine as a companion. The later `architect` skill turns\nan approved Story into code shapes within this spine; it does not replace or override it.\n\nAdapted from BMad Method's Architecture Spine workflow (MIT, BMad Code, LLC).\n",{"name":5,"license":15,"description":7},"main","beda2ad5b6cc4caf3b0f62bc488106ae1d319f8e","plugins\u002Fmonolithic-dev-harness\u002Fskills\u002Farchitecture-spine",0,"https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness","https:\u002F\u002Fmonolithic-dev-harness.balmyangel65.chatgpt.site\u002F","https:\u002F\u002Fgithub.com\u002FMonolith-INC","Agentical Monolithics Cognitivity","2026-11-14 19:32:36",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Monolith-INC\u002Fmonolithic-dev-harness --skill architecture-spine",{"tool":39,"command":40},"bunx","bunx skills add Monolith-INC\u002Fmonolithic-dev-harness --skill architecture-spine",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Monolith-INC\u002Fmonolithic-dev-harness --skill architecture-spine","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Farchitecture-spine\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fspine-template.md","REFERENCE","参考文档",1458,"https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Farchitecture-spine\u002Freferences\u002Fspine-template.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7D7D832ZX48F36GB1F76PST","validate-artifact","Validate a single agile artifact (Epic, Feature, User Story, or Task) against the toolkit rule set. Use when the user asks to \"validate this story\u002Ffeature\u002Fepic\", \"check this ticket\", \"is this artifact ready?\", or provides a local draft path or provider item and wants a quality report. Accepts a local draft or a tracker work item. Runs all checks non-blocking and emits a terminal report + persisted report. One artifact per invocation.","https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fvalidate-artifact\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7D7C4SS2NP2RPWVV1MCKV1P","split-story","Lateral story-sizing skill. Takes a single User Story and determines if it should be split, how many sub-stories to create, and what split pattern to use — then drafts sub-stories and hands them off. Use when the user asks \"split this story\", \"is this story too big?\", \"analyze this story for sizing\", or provides an artifacts path \u002F tracker id \u002F file path \u002F raw text and wants a split recommendation. One story per invocation.","https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fsplit-story\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7D7ACZA52N346HGSMMJZNB4","research-decision","Research a product, market, domain, competitor, user, or technical question in service of a named decision, producing a cited decision brief. Use when planning depends on current evidence rather than more ideation.","https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fresearch-decision\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7D7A1TWTKH944PBW4TZAN8B","product-spec","Distill an idea, brief, PRD, UX contract, architecture spine, issue, or mixed notes into a compact canonical product contract with stable capabilities and companions. Use before backlog decomposition when intent is defined; update or validate an existing product spec through the same skill.","https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fproduct-spec\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7D79VZH4BJPBF85MBG0W5T4","product-requirements","Create, update, or validate a right-sized Product Requirements Document with stable requirements, explicit scope, user journeys where useful, and measurable outcomes. Use for multi-person or multi-epic alignment; skip it when a concise product spec is enough.","https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fproduct-requirements\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7D79QNTG9953KQCM4QZ6QSM","product-brief","Create, update, or validate a concise product brief that captures a clear concept, its users, value, scope, and success criteria. Use when the user wants a one- or two-page product narrative before a PRD or product spec.","https:\u002F\u002Fgithub.com\u002FMonolith-INC\u002Fmonolithic-dev-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fmonolithic-dev-harness\u002Fskills\u002Fproduct-brief\u002FSKILL.md",[],[]]