Scout
Enter scout mode — a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Blueprint
Use when you have a spec or requirements for a multi-step task, before touching code
Diagnose
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Redgreen
Use when implementing any feature or bugfix, before writing implementation code
Craft
Create distinctive, production-grade frontend interfaces with high design quality. Auto-stacked onto an implementation path when a task involves frontend/UI work — pages, components, layouts, styles, interactions. Also available on demand as tn:craft.
Cosmosmith Product Discovery
Turn a rough product idea, vague user desire, or early "create a world" concept into a concise Cosmosmith idea brief. Use when the user has not yet provided a clear problem, target user, first valuable slice, or acceptance criteria; may use web research when market context is current or competitive.
Compass
Use when starting any conversation — establishes how to find and use Techneering skills, requiring skill invocation before ANY response including clarifying questions
Forge
Implement tasks from a change. Use when the user wants to start or continue implementation of an existing change.
Draft
Propose a new change with all artifacts generated in one step. Use when the user wants to describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
Assemble
Use when executing implementation plans with independent tasks in the current session
Cosmosmith Qa Verifier
Verify Cosmosmith tasks against acceptance criteria and produce QA evidence. Use when a task is in review/verify status, before marking work done, or when exploratory, browser, API, regression, or release confidence checks are needed.
Cosmosmith Devops Release
Prepare build, CI, environment, deployment, monitoring, rollback, and release readiness for a Cosmosmith project. Use when tasks approach release, when setup/deploy commands are missing, or when current platform docs are needed.
Cosmosmith Frontend Engineer
Implement frontend task slices from a Cosmosmith task ledger. Use when task.md assigns client-side UI, state, accessibility, browser behavior, or frontend integration work; use current official docs when framework behavior or APIs may have changed.
Audit
Verify implementation matches change artifacts — dual-layer verification of code vs spec compliance and code vs real requirements. Use after implementation is complete.
Gate
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs — requires running verification commands and confirming output before making any success claims; evidence before assertions always
Cosmosmith Market Research
Research current competitors, analogue products, user expectations, pricing, regulations, and ecosystem patterns for a Cosmosmith idea. Use after product discovery or whenever product, design, architecture, QA, or DevOps decisions depend on current external facts.
Inspect
Use after tn:audit passes, when completing major features, or before merging — dispatches a global cross-task code review covering consistency, architecture, and security (distinct from tn:assemble's per-task review)
Cosmosmith Spec Governor
Convert Cosmosmith idea and research briefs into proposal, design, and task ledger artifacts. Use after product discovery, when a rough idea needs an OpenSpec-like proposal, buildable design, and claimable tasks with acceptance checks and verification evidence.
Cosmosmith Backend Engineer
Implement backend task slices from a Cosmosmith task ledger. Use when task.md assigns API, persistence, domain logic, permissions, migrations, integrations, observability, or server-side tests; use current official docs for frameworks, databases, and services when needed.
Vault
Archive a completed change — delta spec merge and move to archive. Use when the user wants to finalize and archive a completed change.
Isolate
Use when starting feature work that needs isolation from current workspace or before executing implementation plans — creates isolated git worktrees with smart directory selection and safety verification
Cosmosmith Ui Ux Designer
Design user flows, screen structure, interaction states, accessibility, and visual direction for a Cosmosmith proposal. Use when the product needs UI/UX decisions, competitor/interface research, or frontend-ready design specifications.
Spark
You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Cosmosmith Architect
Design architecture, boundaries, data flow, reliability, security, and integration strategy for a Cosmosmith proposal. Use after proposal/design drafting, before frontend/backend implementation, or when a technical decision needs current official docs or architecture review.
Cosmosmith Project Rules
Generate or update project instruction files for Cosmosmith-governed projects. Use when the user wants AGENTS.md, CLAUDE.md, Cursor rules, Copilot instructions, OpenCode, Trae, or other editor/agent rules created from Cosmosmith conventions, or when they ask how agents should load and follow project rules.
Ship
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion by presenting structured options for merge, PR, or cleanup
Cosmosmith Governance Review
Review Cosmosmith artifacts, task ledgers, generated project rules, and skill outputs for coherence, layer separation, missing evidence, and rule drift. Use before marking Cosmosmith planning or implementation tasks done, after spec generation, or when project rules and generated rules may have diverged.