Skills in this repository
SkillsMP has collected 71 skills from outfitter-dev/trails. Open a skill to review its source and details.
outfitter-dev/trailsShowing 31 of 71 collected skills.
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.
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.
Compatibility entry for older public-union review prompts. Use Trails Warden's public-output discriminant rule and the building-trails owner-first workflow.
Use when reviewing Trails-owned framework code for Result-shaped failures, resource and cwd boundaries, app loading, and documented host construction exceptions.
Draft or review Trails docs, ADRs, README content, release notes, examples, agent guidance, and prose-heavy changes with one contributor editorial workflow. Use for writing, restructuring, or editorial readiness checks.
Compatibility entry for the retired Trails language-styleguide name. Route all Trails drafting and editorial review through trails-editorial.
Compatibility entry for older primitive-parity prompts. Use building-trails to classify deliberate scope, user-facing gaps, and unsupported symmetry pressure.
Compatibility entry for older Warden-classification prompts. Use building-trails and the canonical Warden contributor guide to place enforceable and advisory findings.
Compatibility entry for older Trails documentation prompts. Route document placement, structure, maintenance, drafting, and review through the singular trails-editorial workflow.
Compatibility entry for older Trails prose prompts. Route prose craft, examples, and vocabulary work through the singular trails-editorial workflow.
Compatibility entry for older Trails writing prompts. Route drafting or review of voice, audience, tone, and stance through the singular trails-editorial workflow.
Use when reviewing Trails error taxonomy, surface error rendering, redaction, retryability, or Result-vs-throw boundaries. Helps distinguish runtime failures from intentional construction and host-boundary throws.
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…
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…
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…
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…
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…
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…
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…
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…
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…