What problem does it solve? Projects often start building before the technical foundation is defined, causing design decisions, slice definitions, and done criteria to be written without knowing the actual stack, deployment path, or security requirements. This Skill captures the tech context once, before design and build, so every downstream phase is technically grounded. ## Core Features & Use Cases - Profile-Based Routing: Loads an established organizational profile (e.g., Bayer Aurora) or interviews the user to build a stack definition from scratch for a general solo project. - Structured Tech Context Document: Produces docs/tech-context.md covering the stack table, architecture constraints, engineering principles, branching model, infrastructure slices, security classification, secrets handling, and runtime configuration. - Security Classification: Classifies the project (Standard, Personal, Financial, Authentication, Multi-tenant, Confidential, Regulated) and gates production deploys behind a compliance acknowledgment when Regulated applies. - Use Case: Before designing screens for a new web app, run this Skill to confirm the frontend framework, deployment path (Railway, Render, Local Mac, etc.), observability tool, and CI/CD preference, producing a single reference document used by design review, planning, and build. ## Quick Start Ask the assistant to establish the tech context for this project before design and planning begin.
