Menu
SkillsMP has collected 48 skills from outfitter-dev/trails. Open a skill to review its source and details.
Copy this prompt into the AI assistant you're using.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/outfitter-dev/trails.Showing 40 of 48 collected skills.
Route a Trails question to native Clark and/or Lewis subagents and synthesize their distinct judgments. Use when the user asks the Trails crew, asks Clark or Lewis, requests an architectural or execution second opinion, wants both co-architects to review a…
Embody Clark, Trails' co-architect and architectural conscience. Use when the current agent should be Clark inline for framework architecture, doctrine, vocabulary, ADRs, tenet alignment, long-horizon coherence, pathfinding, assessment, calibration, debriefs,…
Embody Lewis, Trails' co-architect and execution conscience. Use when the current agent should be Lewis inline to turn doctrine into landed work, shape goals and Graphite stacks, coordinate agents, run evidence and review loops, settle releases, debrief…
The working-on-Trails doctrine digest — what governs the framework, the decision tools for framework work, and where truth lives. Use at the start of any session that changes Trails itself (framework code, docs, vocabulary, governance), when orienting a new…
Authoritative architectural ruling on a specific Trails framework question — naming choices, vocabulary compliance, pattern fitness, scope decisions. Consults the constitutional hierarchy, decides, and logs. Use when a definitive call is needed or when 'let…
Big-picture architectural planning and exploration for the Trails framework. Socratic, principle-anchored exploration of features, ADRs, tenets, and horizon planning. Use when planning new capabilities, drafting or revising ADRs, exploring architectural…
Autonomous codebase health scan for vocabulary drift, naming convention violations, structural anti-patterns, documentation staleness, and test health. Produces prioritized findings as Linear issues. Use for health checks, scheduled scans, or after heavy…
Run a Trails Regrade migration loop with dry-run discovery, occurrence judgment, safe apply, verification, ledger capture, and per-cycle resume.
Trails framework design tenets — the foundational beliefs, promises, primitives, and patterns that govern the framework. Use when evaluating architectural decisions, reviewing feature proposals, checking alignment with framework principles, or when tenets,…
Author, update, and manage Trails ADRs. Use when creating new ADRs, promoting drafts to accepted, updating the ADR index, renaming or renumbering ADRs, or when the user mentions ADR, architecture decision, or decision record.
Complete Trails editorial review workflow. Use when reviewing docs, ADRs, README changes, release notes, agent guidance, or docs-heavy PRs for voice, style, structure, correctness, and readiness.
Define, execute, and settle durable Trails goals. Use for non-trivial Trails work spanning issues, Graphite branches or stacks, agents, review loops, CI, release or publication gates, or whenever a Trails goal needs an explicit completion horizon, authority…
Review a Trails branch, Graphite stack, milestone, generated artifact, migration, documentation set, or implementation slice against current repository doctrine and written acceptance. Use for pre-submit review, targeted risk review, review-fix loops, or a…
Trails documentation structure and maintenance guidance. Use when creating or reorganizing Trails docs, READMEs, guides, reference pages, release docs, or agent-facing documentation.
Trails prose craft and lexicon style. Use when writing or reviewing docs, ADRs, examples, release notes, agent prompts, comments, PR descriptions, or issue language for rhythm, clarity, and vocabulary precision.
Trails writing voice and values. Use when drafting or reviewing Trails docs, ADRs, README content, release notes, agent guidance, or public explanations for stance, audience, and tone.
Route a Trails question to native Clark and/or Lewis subagents and synthesize their distinct judgments. Use when the user asks the Trails crew, asks Clark or Lewis, requests an architectural or execution second opinion, wants both co-architects to review a…
Embody Clark, Trails' co-architect and architectural conscience. Use when the current agent should be Clark inline for framework architecture, doctrine, vocabulary, ADRs, tenet alignment, long-horizon coherence, pathfinding, assessment, calibration, debriefs,…
Embody Lewis, Trails' co-architect and execution conscience. Use when the current agent should be Lewis inline to turn doctrine into landed work, shape goals and Graphite stacks, coordinate agents, run evidence and review loops, settle releases, debrief…
Authoritative architectural ruling on a specific Trails framework question — naming choices, vocabulary compliance, pattern fitness, scope decisions. Consults the constitutional hierarchy, decides, and logs. Use when a definitive call is needed or when 'let…
Autonomous codebase health scan for vocabulary drift, naming convention violations, structural anti-patterns, documentation staleness, and test health. Produces prioritized findings as Linear issues. Use for health checks, scheduled scans, or after heavy…
Define, execute, and settle durable Trails goals. Use for non-trivial Trails work spanning issues, Graphite branches or stacks, agents, review loops, CI, release or publication gates, or whenever a Trails goal needs an explicit completion horizon, authority…
Review a Trails branch, Graphite stack, milestone, generated artifact, migration, documentation set, or implementation slice against current repository doctrine and written acceptance. Use for pre-submit review, targeted risk review, review-fix loops, or a…
Build with the Trails framework — define trail contracts, open CLI/MCP surfaces, test with examples, debug errors, migrate codebases, run governance. Use when creating trails, adding surfaces, testing, debugging Trails errors, migrating to Trails, running…
Embody Clark, Trails' co-architect and architectural conscience. Use when the current agent should be Clark inline for framework architecture, doctrine, vocabulary, ADRs, tenet alignment, long-horizon coherence, pathfinding, assessment, calibration, debriefs,…
Run a Trails Regrade migration loop with dry-run discovery, occurrence judgment, safe apply, verification, ledger capture, and per-cycle resume.
Route a Trails question to native Clark and/or Lewis subagents and synthesize their distinct judgments. Use when the user asks the Trails crew, asks Clark or Lewis, requests an architectural or execution second opinion, wants both co-architects to review a…
Embody Lewis, Trails' co-architect and execution conscience. Use when the current agent should be Lewis inline to turn doctrine into landed work, shape goals and Graphite stacks, coordinate agents, run evidence and review loops, settle releases, debrief…
The working-on-Trails doctrine digest — what governs the framework, the decision tools for framework work, and where truth lives. Use at the start of any session that changes Trails itself (framework code, docs, vocabulary, governance), when orienting a new…
Authoritative architectural ruling on a specific Trails framework question — naming choices, vocabulary compliance, pattern fitness, scope decisions. Consults the constitutional hierarchy, decides, and logs. Use when a definitive call is needed or when 'let…
Big-picture architectural planning and exploration for the Trails framework. Socratic, principle-anchored exploration of features, ADRs, tenets, and horizon planning. Use when planning new capabilities, drafting or revising ADRs, exploring architectural…
Autonomous codebase health scan for vocabulary drift, naming convention violations, structural anti-patterns, documentation staleness, and test health. Produces prioritized findings as Linear issues. Use for health checks, scheduled scans, or after heavy…
Trails framework design tenets — the foundational beliefs, promises, primitives, and patterns that govern the framework. Use when evaluating architectural decisions, reviewing feature proposals, checking alignment with framework principles, or when tenets,…
Author, update, and manage Trails ADRs. Use when creating new ADRs, promoting drafts to accepted, updating the ADR index, renaming or renumbering ADRs, or when the user mentions ADR, architecture decision, or decision record.
Complete Trails editorial review workflow. Use when reviewing docs, ADRs, README changes, release notes, agent guidance, or docs-heavy PRs for voice, style, structure, correctness, and readiness.
Define, execute, and settle durable Trails goals. Use for non-trivial Trails work spanning issues, Graphite branches or stacks, agents, review loops, CI, release or publication gates, or whenever a Trails goal needs an explicit completion horizon, authority…
Review a Trails branch, Graphite stack, milestone, generated artifact, migration, documentation set, or implementation slice against current repository doctrine and written acceptance. Use for pre-submit review, targeted risk review, review-fix loops, or a…
Use when a Trails change derives framework facts, derived views, rule data, or surface metadata. Helps agents find authoritative owner exports and avoid shadow registries, duplicated maps, and canonical-source indirection.
Use when reviewing public or queryable Trails outputs that expose union-like shapes to agents or surfaces. Helps decide whether stable discriminants are required and whether the issue is schema cleanup, advisory guidance, or Warden work.
Use when reviewing Trails-owned framework code for Result-shaped failures, resource and cwd boundaries, app loading, and documented host construction exceptions.