stratt://dev/
19 units across 5 types: chain, role, rule, supply, task
| Slug | Type | Status | Fingerprint | Description |
|---|---|---|---|---|
| sol-1-boot | chain | draft | ●Verified | Canonical project bootstrap chain. Parses intake, elects stack, generates schemas, scaffolds directory, bootstraps CI, and performs final planner gate review. Two gate checkpoints enforce review at stack election and final approval. |
| architect | role | draft | ●Verified | Systems architect with full-stack expertise spanning TypeScript, Go, and infrastructure-as-code. Decomposes requirements into bounded contexts and produces ADR-ready rationale for design decisions. |
| ci-cd-operator | role | draft | ●Verified | CI/CD pipeline engineer and deployment automation specialist. Designs pipelines for reproducibility, cache efficiency, and zero-downtime deploys. |
| documenter | role | draft | ●Verified | Technical writer specialising in developer documentation, Architecture Decision Records, changelogs, and API reference generation. |
| planner | role | draft | ●Verified | Project planner and sole gate authority for the Pathfinder council. Decomposes projects into phased milestones, assesses risk and blast radius, and renders final gate decisions. |
| reviewer | role | draft | ●Verified | Adversarial code reviewer and security auditor. Assumes every change is guilty until proven otherwise. Cannot be bypassed in pre-merge chains. |
| test-architect | role | draft | ●Verified | Test strategy architect covering unit, integration, and end-to-end verification. Designs test suites that verify contracts and boundary conditions, not implementation details. |
| adr-template-requirements | rule | draft | ●Verified | Mandatory structure for Architecture Decision Records ensuring consistent documentation of design decisions across the dev domain. |
| code-review-standards | rule | draft | ●Verified | Mandatory code review standards for the dev domain covering security, performance, API contracts, and test coverage requirements. |
| incident-severity-classification | rule | draft | ●Verified | Standard severity classification for incidents in the dev domain with blast radius assessment requirements. |
| go-project-conventions | supply | draft | ●Verified | Reusable conventions for Go projects including module layout, error handling, testing patterns, and build configuration. |
| typescript-project-conventions | supply | draft | ●Verified | Reusable conventions for TypeScript projects including module format, compiler settings, linting, and dependency management patterns. |
| boot-review | task | draft | ●Verified | Final planner gate review of all boot sequence outputs. Assesses risk, verifies completeness, and renders the go/no-go decision for the project bootstrap. |
| ci-bootstrap | task | draft | ●Verified | Generate CI/CD pipeline configuration files matching the elected stack and directory structure, using GitHub Actions with reusable workflow patterns. |
| directory-scaffold | task | draft | ●Verified | Create the project directory structure and scaffold initial files matching the elected stack and generated schemas. |
| domain-map | task | draft | ●Verified | Map project intake requirements to STRATT domain classification. Determines if a problem belongs to dev, ops, docs, or a multi-domain pattern. |
| intake-parse | task | draft | ●Verified | Parse a raw project intake document or idea brief into structured requirements with functional and non-functional categories, constraints, and flagged ambiguities. |
| schema-generation | task | draft | ●Verified | Generate data schemas and type definitions from parsed requirements using the elected technology stack's native schema tooling. |
| stack-election | task | draft | ●Verified | Evaluate technology stacks against parsed requirements and constraints, produce a ranked selection with ADR-format rationale documenting the decision and trade-offs. |