메뉴
This skill should be used when creating session handoffs, logging research findings, or reading previous trail notes. Triggers include handoff, session continuity, log note, trail notes, or when ending a session.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | trails |
| description | This skill should be used when creating session handoffs, logging research findings, or reading previous trail notes. Triggers include handoff, session continuity, log note, trail notes, or when ending a session. |
| metadata | {"version":"1.0.2"} |
Session continuity through structured handoffs and freeform logs.
<when_to_use>
</when_to_use>
| Command | Purpose |
|---|---|
/trail:handoff | Create structured handoff note for session continuity |
/trail:log <slug> | Create freeform timestamped log note |
/trail:read [options] | Read recent trail notes |
Handoffs are the atomic unit of session continuity. Create one at the end of each session.
# Handoff
> YYYY-MM-DD HH:MM · Session `<short-id>`
## Done
- Completed item 1
- Completed item 2
## State
Current state of work:
- What's in progress
- What's blocked
- Key decisions made
## Next
- [ ] First priority task
- [ ] Second priority task
- [ ] Lower priority item
Logs are freeform notes for capturing anything worth preserving.
# Title Derived From Slug
> YYYY-MM-DD HH:MM · Session `<short-id>`
{ freeform content — research findings, technical discoveries,
meeting notes, ideas, observations, etc. }
When working as a subagent, pass the parent session ID to group related notes:
# Handoff with parent context
bun ${CLAUDE_PLUGIN_ROOT}/skills/trails/scripts/handoff.ts \
--session "$CHILD_SESSION" \
--parent "$PARENT_SESSION"
# Log with parent context
bun ${CLAUDE_PLUGIN_ROOT}/skills/trails/scripts/log.ts \
--slug "api-findings" \
--session "$CHILD_SESSION" \
--parent "$PARENT_SESSION"
This creates notes in a subdirectory: .trail/notes/YYYY-MM-DD/<parent-session>/
# Today's notes (all types)
/trail:read
# Just handoffs
/trail:read --type handoff
# Just logs
/trail:read --type log
# Last 3 days
/trail:read --days 3
# Limit output
/trail:read --lines 100
.trail/
├── notes/
│ └── YYYY-MM-DD/
│ ├── handoff-YYYYMMDDhhmm-<session>.md
│ ├── YYYYMMDDhhmm-<slug>.md
│ └── <parent-session>/ # Subagent notes
│ ├── handoff-YYYYMMDDhhmm-<child>.md
│ └── YYYYMMDDhhmm-<slug>.md
├── plans/ # Implementation plans
└── artifacts/ # Research, ADRs, etc.
Pattern: [prefix-]YYYYMMDDhhmm[-suffix].md
| Type | Prefix | Suffix | Example |
|---|---|---|---|
| Handoff | handoff | session ID | handoff-202601221430-f4b8aa3a.md |
| Log | none | slug | 202601221430-api-research.md |
The timestamp (YYYYMMDDhhmm) is the anchor — files remain sortable and portable even if moved.
When resuming work:
/trail:read --type handoff to see recent handoffsBefore ending a session:
/trail:handoff to create a handoff notePatterns for @outfitter/daemon including lifecycle management, IPC communication, health checks, and PID files. Use when building background services, daemons, or when "daemon", "IPC", "health check", "background service", or "@outfitter/daemon" are mentioned.
Creates handlers, CLI commands, MCP tools, and daemon services following Outfitter Dev Kit conventions. Use when adding new components to a project, scaffolding code, or when "create handler", "new command", "add tool", or "daemon service" are mentioned.
Deep patterns for @outfitter/mcp including tool registration, Zod schemas, resources, and server configuration. Use when building MCP servers, registering tools, defining resources, or when "MCP server", "MCP tool", "registerTool", or "@outfitter/mcp" are mentioned.
Generates patterns, templates, and guides for @outfitter/* packages. Covers transport-agnostic handler systems, Result types, error taxonomy, and package APIs. Use when working with @outfitter/*, Result types, Handler contract, error taxonomy, or when Result, Handler, ValidationError, NotFoundError, OutfitterError, or package names like contracts, cli, mcp, schema, tui, daemon, config, logging are mentioned.
Verify Outfitter compliance in a codebase. Scans for anti-patterns (throws, console, hardcoded paths) and produces a severity-ranked compliance report. Use for pre-commit checks, code review, or migration validation.
Submit feedback to the Outfitter team via GitHub issues. Use after discovering bugs, missing features, unclear docs, or improvement opportunities in @outfitter/* packages.