skills.rest
outfitter-dev
outfitter-devOFFICIAL
Explore all skills by this author →
Website𝕏@outfitter_devGitHub

trails-primitive-parity

Analyze Trails primitives for maturity gaps against expected trail surfaces.

4|1|Updated Mar 28, 2026
Search Tags:#audit#docs#parity#primitives#trails#topo
One-click install
npx skills add https://github.com/outfitter-dev/trails --skill trails-primitive-parity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trails-primitive-parity
Source: https://github.com/outfitter-dev/trails/tree/main/plugin/skills/trails-primitive-parity
Command: npx skills add https://github.com/outfitter-dev/trails --skill trails-primitive-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluates Trails primitives for maturity alignment with the surfaces they enable, surfacing deliberate gaps, user-facing deficiencies, and future-facing symmetry pressures to guide focused improvements.

Core Features & Use Cases

  • Systematically compare a primitive's capabilities against expected trail surfaces and behaviors.
  • Classify gaps into deliberate scope, user-facing gaps, agent ergonomics debt, or parity pressures.
  • Produce evidence-based recommendations and define follow-up scope for docs, tests, or surface changes.

Quick Start

Analyze a Trails primitive and report its maturity gaps with actionable recommendations.

Frequently Asked Questions about trails-primitive-parity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Trails primitive maturity and surface coverage gaps?▼

Classify Trails primitive parity gaps by analyzing surface coverage across docs, ADRs, tests, and package exports. Gaps are categorized into deliberate scope, user-facing deficiencies, agent ergonomics debt, or future-facing symmetry pressures to guide improvements.

What does a primitive parity audit check for in Trails documentation and tests?▼

A primitive parity audit checks Trails documentation, ADRs, package exports, tests, and surface coverage to determine maturity scope and impact. It reveals deliberate gaps, user-facing deficiencies, and symmetry pressures to guide focused improvements.

How do I check if a Trails primitive has complete surface coverage before release?▼

Check Trails primitive surface coverage by auditing documentation, ADRs, package exports, and tests against expected trail surfaces. This reveals maturity gaps and provides evidence-based parity findings with recommended follow-ups.

Can I use primitive parity findings to plan documentation and test follow-ups for Trails?▼

Yes, primitive parity findings define follow-up scope for Trails documentation, tests, or surface changes. Evidence-based recommendations guide focused improvements by addressing deliberate scope, user-facing gaps, and agent ergonomics debt.

What is the difference between user-facing gaps and deliberate scope in Trails primitive parity?▼

User-facing gaps are deficiencies affecting trail surface consumers, while deliberate scope represents intentionally excluded capabilities. Primitive parity analysis classifies these differences alongside agent ergonomics debt and parity pressures to determine maturity scope and impact.

Related Skills

Explore More Software Engineering Skills→
ivyivy
9

export-log

Export Claude conversation logs to markdown with metadata.

Community
Intermediate
AcidicSoilAcidicSoil
1

validate-architecture

Validate architecture documents for completeness and quality using a rule-based checklist.

Community
Advanced
Vivekmano27Vivekmano27

agent-native-design

Map UI actions to atomic agent tools with parity mapping and runtime specifications.

Community
Advanced
OpenLaborOpenLabor
4

Tech Stack Evaluation

Evaluate technology choices and output a weighted comparison with rationale and migration plan.

Official
Advanced