mit einem Klick
devlog
// Write or update a devlog entry in the devlog directory. Use when the user asks to write a devlog, record a decision, document what happened, or says "write up what we did".
// Write or update a devlog entry in the devlog directory. Use when the user asks to write a devlog, record a decision, document what happened, or says "write up what we did".
Use when working with Trailblaze — natural-language device control for coding agents across iOS, Android, and web, with replayable `.trail.yaml` files as the artifact. Trigger on mentions of Trailblaze, the `trailblaze` CLI, `.trail.yaml` files, trailmaps, waypoints, or requests to drive / author / debug / run UI tests on iOS / Android / web — including authoring a custom typed scripted tool, composing an agent's tool surface, or writing a trailmap.
Use when validating or evaluating Trailblaze's out-of-box (OOB) user experience — does what the `trailblaze` skill claims actually match the real installed CLI? Triggers on requests to "validate the Trailblaze skill", "test the Trailblaze OOB experience", "evaluate Trailblaze UX", "check if the skill matches the CLI", "audit the Trailblaze CLI for new-user friction", or running an OOB regression check after the framework changes.
| name | devlog |
| description | Write or update a devlog entry in the devlog directory. Use when the user asks to write a devlog, record a decision, document what happened, or says "write up what we did". |
Write or update a devlog entry in the devlog directory.
Devlog entries are development journal posts that capture decisions, discoveries, and plans as work happens. They're written for the team — concise, honest, and useful for future reference.
Filename: YYYY-MM-DD-<topic-slug>.md
Use today's date and a short kebab-case topic slug.
---
title: "Short Descriptive Title"
type: devlog
date: YYYY-MM-DD
---
# Title
## Summary
1-3 sentences on what this entry covers.
## <Sections as needed>
Use whatever sections make sense for the content. Common ones:
- What Changed
- Key Decisions (and rationale)
- What We Learned
- Open Questions
- Future Work
Keep it direct. No filler. Write like you're explaining to a teammate who will read this in 3 months.
| Field | Required | Values |
|---|---|---|
title | Yes | Short descriptive title |
type | Yes | decision (architectural/technical choice) or devlog (development note) |
date | Yes | YYYY-MM-DD format |
Use type: decision when recording a significant architectural or technical choice. Use type: devlog for development notes, debugging sessions, and implementation details.
When the user says /devlog, ask what topic to write about if it's not clear from context. If you've been working on something substantial in the current session, suggest writing about that.