| name | devlog |
| description | Write implementation devlogs that capture current session progress, learnings, related artifacts, and next steps. Use when the user asks for a devlog or WIP devlog. |
Devlog
Use this skill when the goal is to persist current implementation context for a later session.
This skill is the replacement for the old devlog command.
Scope
Use this skill for requests like:
- "
devlog"
- "write a devlog"
- "create a WIP devlog"
- "document this session"
Workflow
- Create
thoughts/shared/devlog/ if needed
- Choose a filename using the
Europe/Stockholm calendar date
- Use a 3-5 word kebab-case session slug
- If the request is work-in-progress, append
_progress.md
- If another entry already exists for that date and slug, append
_2, _3, and so on
- Fill in the template below using current session context
Filename patterns:
YYYY-MM-DD_session-slug.md
YYYY-MM-DD_session-slug_progress.md
Statuses:
✅ COMPLETED
🔄 PARTIAL
❌ BLOCKED
The devlog should include related artifacts when known:
related_spec
related_adr
related_plan
related_research
related_issues
Template