stack
Records the technical layers of a project in docs/architecture/stack.md, the AI Unified Process stack file: which technology and which layer skill builds and tests the migration, persistence, service, API, UI, and end-to-end layers, the integration layer, the module layout, the API contract, and the build and test commands. Detects the stack from pom.xml, package.json, and the source tree, discovers the installed layer skills from their references/layer.md, and asks in a new project. Works next to any architecture documentation (arc42, C4, 4+1, or none), which it reads but never writes. /use-case-implement, /use-case-test, and /use-case-coverage read the file. Use when the user asks to "set up the stack", "choose the stack", "which layers does this project have", "we only need a REST API", "add a UI layer", "add a REST API next to the UI", or mentions layer plugins or a technology stack for construction. Also trigger when /use-case-implement or /use-case-test finds no stack file.
Pinned to revision dbb4e27b6d25, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.