Guards a project's telos/purpose hierarchy before scope, architecture, dependency, integration, roadmap, or implementation decisions. Use when the user asks should we build this?, does this fit?, where should this live?, what design aligns?, or when work may change product purpose, user experience, contracts, modules, or tests. Reads TELOS.md, telos/TELOS.md, telos/specs, and @telos annotations; initializes missing Telos context; evaluates L4 Purpose, L3 Experience, L2 Contract, and L1 Function before implementation.
Use when preparing, submitting, finishing, or cleaning up a pull request, especially when draft PRs, Greptile feedback, review comments, or merge-readiness work need end-to-end handling.
Run pre-implementation AI consulting engagements—company research, discovery, maturity assessment, opportunity prioritization, and proposal/SOW/roadmap creation—and use only for advisory work, not implementation.
Guide annuity and life-insurance sales workflows—discovery, suitability, product selection, objections, closing, and servicing—when supporting licensed insurance sales conversations or deliverables.
Generate API reference documentation from source code—endpoints, schemas, auth, errors, and examples—when the task is to document an existing API rather than design or implement one.
Generate release notes and changelogs from git history with SemVer classification, grouped changes, and migration notes when documenting what changed between versions or refs.
Build, validate, serialize, or parse CNCF CloudEvents v1.0 payloads and transports when the task explicitly involves CloudEvents envelopes, ce-* headers, or structured/binary event delivery.
Review existing code or diffs for bugs, security issues, performance problems, maintainability risks, and test gaps when the user wants evaluation, not new implementation.