stratt://core/
61 units across 5 types: chain, role, rule, supply, task
| Slug | Type | Status | Fingerprint | Description |
|---|---|---|---|---|
| 001-gap-analysis | chain | published | ·Not fingerprinted | Systematic current-state assessment protocol with anti-hallucination enforcement. Loads project context, identifies gaps between current and desired state, and produces a verified gap analysis report. |
| 002-strategic-planning | chain | published | ·Not fingerprinted | Transforms gap analysis findings into actionable tasksets. Defines strategic approach, architectural philosophy, and sequenced implementation plan with dependencies and success criteria. |
| 003-technical-design | chain | published | ·Not fingerprinted | Produces detailed technical architecture and specifications for a taskset. Defines component interfaces, API contracts, database schemas, and technology stack decisions with rollback procedures. |
| 004-gated-execution | chain | published | ·Not fingerprinted | Gated implementation protocol that executes code changes in controlled phases. Enforces pre-execution verification, incremental commits, and rollback readiness throughout the implementation process. |
| 005-qa-and-validation | chain | published | ·Not fingerprinted | Quality assurance protocol for validating implementations. Runs test suites, verifies component integration, checks quality gates, and produces validation reports with technical debt scoring. |
| 006-knowledge-transfer | chain | published | ·Not fingerprinted | Documentation and knowledge transfer protocol for completed implementations. Produces technical docs, API references, runbooks, and onboarding materials tailored to multiple audience types. |
| adversarial-security-audit | chain | draft | ·Not fingerprinted | Think like an attacker — systematically map attack surfaces, analyze vulnerabilities using XML attack trees, and produce a prioritized remediation plan |
| brand-asset-generation-pipeline | chain | draft | ·Not fingerprinted | Multi-step agent-to-agent chain for generating brand assets. Orchestrates brand normalization, prompt generation, model routing, and asset validation across cooperating agents. |
| codebase-reverse-engineering-atlas | chain | draft | ·Not fingerprinted | Drop into any unknown codebase and produce a complete technical atlas — architecture maps, dependency graphs, pattern inventory, and onboarding documentation |
| domain-extension-pipeline | chain | draft | ●Verified | 10-phase meta-chain for extending STRATT to new professional domains. Orchestrates domain discovery, workflow mapping, taxonomy design, and unit generation. Produces 20-50 reusable STRATT units tailored to a specific domain. Every phase has a human gate checkpoint. |
| local-to-remote-migration | chain | draft | ·Not fingerprinted | 5-phase pipeline for migrating local directories to GitHub organization repositories with architectural assessment and validation |
| technical-debt-quantifier | chain | draft | ·Not fingerprinted | Deterministic, evidence-based technical debt assessment with weighted scoring matrices and ROI-based prioritization |
| veritas-prompt-refinement-intelligence-pipeline | chain | draft | ·Not fingerprinted | Complete n8n automation suite for prompt library ingestion, classification, refinement, evaluation, decomposition, graduation, and integration with Ariel baselining and Traceo traceability |
| zero-to-production-infrastructure | chain | draft | ·Not fingerprinted | Take any application from local development to production-grade deployment infrastructure — containers, CI/CD, observability, and security hardening |
| domain-analyst | role | draft | ●Verified | Agent persona that orchestrates the domain extension pipeline. Runs discovery, workflow mapping, taxonomy design, and validation phases. The systematic decomposer that understands domain structure deeply enough to ask clarifying questions and identify gaps. |
| every-phase-gated | rule | draft | ●Verified | Mandatory gate checkpoint at every phase of the domain extension pipeline. No phase proceeds without human approval. Ensures domain expert validates outputs before proceeding to the next phase. |
| no-phantom-domain-concepts | rule | draft | ●Verified | Integrity constraint preventing reference to domain concepts without verification against primary sources. All domain-specific terms, rules, and workflows must be traceable to the domain expert's input or published materials. |
| anti-hallucination-framework | supply | draft | ·Not fingerprinted | Reusable anti-hallucination rules and verification checkpoints for tool-assisted workflows |
| attack-tree-framework | supply | draft | ·Not fingerprinted | Framework for constructing attack trees that model threat scenarios as hierarchical goal decompositions with AND/OR relationships |
| compact-item-meta | supply | draft | ·Not fingerprinted | Instruction fragment for generating Docusaurus MDX frontmatter metadata. Categorizes documents (prompts, static data, knowledge graphs) and produces enriched properties following systems design standards. |
| decision-tree-framework | supply | draft | ·Not fingerprinted | Reusable framework for building branching diagnostic decision trees with node types, traversal rules, and output formatting |
| define-corpus-blocks | supply | draft | ·Not fingerprinted | Template fragment for generating detailed YAML corpus sections per system domain. Includes stream definitions, consumer specs, event schemas, and retention policies for event-driven architectures. |
| domain-extension-rfc-template | supply | draft | ●Verified | Output template for domain extension pipeline. Structured format for the final RFC document that contains the complete domain extension specification including profile summary, workflow map, taxonomy, rules, supplies, tasks, chains, and roles. |
| domain-profile-template | supply | draft | ●Verified | Structured questionnaire that captures everything needed to build a domain extension. Nine sections: About You, Your Domain, Your Workflow, Where Your Time Goes, Your Rules and Standards, Your Tools, Your Concerns About AI, Your Secret Weapon, The People Around You. |
| error-handling-patterns | supply | draft | ·Not fingerprinted | Error categorization, severity levels, and rollback procedures for multi-step workflows |
| evidence-collection-protocol | supply | draft | ·Not fingerprinted | Standardized protocol for collecting, documenting, and referencing evidence during audits and assessments |
| pattern-taxonomy-framework | supply | draft | ·Not fingerprinted | Hierarchical taxonomy for classifying architectural and code patterns observed in a codebase |
| severity-scoring-matrix | supply | draft | ·Not fingerprinted | Standardized severity scoring framework with weighted dimensions for quantifying and prioritizing findings across audits and assessments |
| subsystem-categorization | supply | draft | ·Not fingerprinted | Taxonomy for classifying directory subsystems into architectural categories (frontend, backend, library, infrastructure, tooling, documentation) |
| with-systems-knowledge | supply | draft | ·Not fingerprinted | Composable suffix fragment that injects distributed systems expertise framing. Provides multiple reasoning-style variants emphasizing modularity, testability, scalability, and engineering discipline. |
| agent-handoff-protocol-for-branding | task | draft | ·Not fingerprinted | Defines the structured handoff protocol between agents in the branding pipeline. Specifies message format, context passing, error escalation, and completion signals for agent-to-agent operations. |
| asa-phase-1-attack-surface-mapping | task | draft | ·Not fingerprinted | Systematically identify and catalog all attack surfaces — external interfaces, authentication boundaries, data flows, and trust boundaries |
| asa-phase-2-vulnerability-analysis | task | draft | ·Not fingerprinted | Build attack trees for identified attack surfaces, analyze vulnerability classes from the selected threat model, and score findings |
| asa-phase-3-risk-scoring-remediation | task | draft | ·Not fingerprinted | Aggregate vulnerability findings, calculate composite risk scores, and generate a prioritized remediation roadmap |
| brand-normalization | task | draft | ·Not fingerprinted | Single-step task to convert a structured project definition (YAML/JSON) into a natural language Brand Anchor suitable for injection into generative AI prompts. |
| chain-composition | task | draft | ●Verified | Phase 6: Compose task units into executable chains. Order tasks by dependency, add gates where domain expert requires human approval, set agent assignments. |
| cra-phase-1-inventory-discovery | task | draft | ·Not fingerprinted | Scan and catalog the complete filesystem structure, detect technology stack, and identify all entry points in an unknown codebase |
| cra-phase-2-dependency-mapping | task | draft | ·Not fingerprinted | Analyze import statements to build internal and external dependency graphs, identify hotspots, and detect circular dependencies |
| cra-phase-3-pattern-recognition | task | draft | ·Not fingerprinted | Identify and classify architectural, design, data, and communication patterns across the codebase using the pattern taxonomy framework |
| cra-phase-4-atlas-generation | task | draft | ·Not fingerprinted | Synthesize all findings into a comprehensive technical atlas with architecture diagrams, component catalog, onboarding guide, and risk register |
| domain-discovery | task | draft | ●Verified | Phase 0: Extract structured requirements from domain expert. Validate profile completeness. Identify any ambiguities or gaps before proceeding to workflow mapping. |
| domain-validation | task | draft | ●Verified | Phase 8: Automated validation of all generated units. Check schema compliance, import resolution, no phantom concepts, and consistency with domain profile. |
| ltm-phase-0-pre-execution-verification | task | draft | ·Not fingerprinted | Verify environment prerequisites, gather user inputs, and analyze directory structure before GitHub migration |
| ltm-phase-1-architectural-assessment | task | draft | ·Not fingerprinted | Categorize subsystems, apply architectural principles, validate segmentation, and present migration plan for approval |
| ltm-phase-2-repository-creation | task | draft | ·Not fingerprinted | Create GitHub repositories with proper configuration, branch protection, and topic tagging |
| ltm-phase-3-code-migration | task | draft | ·Not fingerprinted | Initialize git repositories, prepare subsystem code, create initial commits, and push to GitHub |
| ltm-phase-4-post-migration-validation | task | draft | ·Not fingerprinted | Validate all repositories for completeness and generate migration summary report |
| rfc-generation | task | draft | ●Verified | Phase 9: Generate the final RFC document. Compile all unit definitions, validation results, and domain profile into a comprehensive domain extension specification document. |
| role-definition | task | draft | ●Verified | Phase 7: Define domain-specific roles (personas) for agents. Each role captures the lens, tone, behaviour expectations, and output format for a particular function. |
| rule-generation | task | draft | ●Verified | Phase 3: Extract domain constraints into STRATT rule units. For each "must always" and "AI must never" statement from the profile, create a rule unit with polarity, scope, and statement. |
| supply-generation | task | draft | ●Verified | Phase 4: Extract templates, checklists, and format guides into STRATT supply units. Reusable fragments that multiple tasks can reference. |
| tag-taxonomy-design | task | draft | ●Verified | Phase 2: Design a domain-specific tag taxonomy. Organize concepts by category (core, workflow, constraints, outputs). Check for overlaps and ambiguities. Output a taxonomy YAML. |
| task-generation | task | draft | ●Verified | Phase 5: Generate STRATT task units for domain workflows. Each workflow phase becomes a task with prompt_body, contract (inputs/outputs), and dependencies. |
| tdq-phase-1-debt-inventory | task | draft | ·Not fingerprinted | Systematically scan the codebase for technical debt indicators across all categories with evidence collection |
| tdq-phase-2-impact-scoring | task | draft | ·Not fingerprinted | Score each debt item using weighted dimensions, apply profile-specific adjustments, calculate ROI, and identify debt clusters |
| tdq-phase-3-remediation-roadmap | task | draft | ·Not fingerprinted | Group scored debt items into themed epics, sequence by ROI and dependencies, and generate a stakeholder-ready remediation report |
| workflow-mapping | task | draft | ●Verified | Phase 1: Decompose domain workflows into phases. For each workflow, identify inputs, outputs, decision points, error-prone areas, and time allocation. Output a structured workflow map. |
| zpi-phase-1-application-assessment | task | draft | ·Not fingerprinted | Analyze the application to determine its runtime requirements, resource needs, external dependencies, and deployment characteristics |
| zpi-phase-2-infrastructure-design | task | draft | ·Not fingerprinted | Generate production-grade infrastructure-as-code: Dockerfiles, orchestration configs, networking, storage, and security configurations |
| zpi-phase-3-deployment-pipeline | task | draft | ·Not fingerprinted | Generate CI/CD pipeline configuration with build, test, security scan, and deploy stages with environment promotion and rollback |
| zpi-phase-4-observability-hardening | task | draft | ·Not fingerprinted | Configure comprehensive observability (logging, metrics, tracing, alerting) and apply security hardening to the deployment |