How do I install the Backtrail Create skill?

Run npx skillmds@latest add ivan-gerasimov-1/backtrail-create in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Backtrail Create skill do?

Route Backtrail creation requests to ADR, FEATURE, or CHANGE creation It is listed under Coding & Dev Tools on SkillMD.

Is Backtrail Create safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Backtrail Create?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Backtrail Create free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Backtrail Create?

ivan-gerasimov-1 (@ivan-gerasimov-1) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Backtrail Create by ivan-gerasimov-1

Name: Backtrail Create
Author: ivan-gerasimov-1

File contents

Purpose

Choose the correct Backtrail creation skill. Do not create or edit Backtrail artifacts directly.

Input

Use the text after this skill invocation as the routing brief.

Prerequisites

Read .backtrail/adl.md, .backtrail/changes.md, .backtrail/features.md, and .backtrail/tasks.md before routing, when they exist.
Use indexes to identify referenced records, current direction, and artifact fit.
If an index is missing, route from the brief; the selected skill handles setup.

Workflow

Check prerequisites.
Durable decision -> backtrail-create-adr.
- Architecture, repository structure, public contracts, generated output, build/test workflow, dependencies, reversibility, or future-work constraints.
User-visible capability/product behavior -> backtrail-create-feature.
- User workflows, acceptance criteria, product behavior, or durable capability specs.
Concrete implementation work without an existing CHANGE scope contract -> backtrail-create-change.
- Bug fixes, local refactors, tests, existing ADR/FEATURE implementation details, copy changes, dependency patch updates, or implementation plans.
Split an existing CHANGE into reviewable implementation checkpoints -> backtrail-create-task.
- Explicit TASK requests, staged implementation plans under one CHANGE, or large/risky CHANGE decomposition.
If exactly one skill matches, immediately hand the original brief to that skill and continue that workflow.
If multiple skills match, ask one clarifying question before routing.
If none match, state that no matching Backtrail creation skill exists, then stop.

Question UX

Use request_user_input when available for two or three meaningful choices.
For routing ambiguity, present only the matching artifact types as choices: ADR, FEATURE, CHANGE, and/or TASK.
If request_user_input is unavailable, ask one concise plain-text question with numbered choices.
Do not claim that a skill can switch modes or force button rendering.

Guardrails

Do not create ADR, FEATURE, CHANGE, TASK, index, config, code, or test files.
Do not invent new Backtrail artifact types beyond documented Backtrail skills.
Do not route to implementation work.
Do not inspect the broader repository unless needed to classify the request.
Preserve the original brief when handing it off to the selected skill.

---name: backtrail-createdescription: Route Backtrail creation requests to ADR, FEATURE, or CHANGE creation---## PurposeChoose the correct Backtrail creation skill. Do not create or edit Backtrail artifacts directly.## InputUse the text after this skill invocation as the routing brief.## Prerequisites- Read `.backtrail/adl.md`, `.backtrail/changes.md`, `.backtrail/features.md`, and `.backtrail/tasks.md` before routing, when they exist.- Use indexes to identify referenced records, current direction, and artifact fit.- If an index is missing, route from the brief; the selected skill handles setup.## Workflow1. Check prerequisites.2. Durable decision -> `backtrail-create-adr`. - Architecture, repository structure, public contracts, generated output, build/test workflow, dependencies, reversibility, or future-work constraints.3. User-visible capability/product behavior -> `backtrail-create-feature`. - User workflows, acceptance criteria, product behavior, or durable capability specs.4. Concrete implementation work without an existing CHANGE scope contract -> `backtrail-create-change`. - Bug fixes, local refactors, tests, existing ADR/FEATURE implementation details, copy changes, dependency patch updates, or implementation plans.5. Split an existing CHANGE into reviewable implementation checkpoints -> `backtrail-create-task`. - Explicit TASK requests, staged implementation plans under one CHANGE, or large/risky CHANGE decomposition.6. If exactly one skill matches, immediately hand the original brief to that skill and continue that workflow.7. If multiple skills match, ask one clarifying question before routing.8. If none match, state that no matching Backtrail creation skill exists, then stop.## Question UX- Use `request_user_input` when available for two or three meaningful choices.- For routing ambiguity, present only the matching artifact types as choices: `ADR`, `FEATURE`, `CHANGE`, and/or `TASK`.- If `request_user_input` is unavailable, ask one concise plain-text question with numbered choices.- Do not claim that a skill can switch modes or force button rendering.## Guardrails- Do not create ADR, FEATURE, CHANGE, TASK, index, config, code, or test files.- Do not invent new Backtrail artifact types beyond documented Backtrail skills.- Do not route to implementation work.- Do not inspect the broader repository unless needed to classify the request.- Preserve the original brief when handing it off to the selected skill.

Frequently asked questions

Backtrail Create