anarlog-workflow
/anarlog-workflow
Execute Anarlog work immediately while recording issues, decisions, progress, and lessons in Linear. Use for Anarlog repository or Anarlog desktop, web, mobile, and API work, including related worktrees and ANLG issues. Explicit brainstorming stays discussion-first. Do not use for unrelated repositories or meeting-data queries.
- Author
- modem-dev ↗
- Repository
- ossrules ↗
- Licence
- MIT
- Last repository change
- 21.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 21.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Execute Anarlog work immediately while recording issues, decisions, progress, and lessons in Linear. Use for Anarlog repository or Anarlog desktop, web, mobile, and API work, including related worktrees and ANLG issues. Explicit brainstorming stays discussion-first. Do not use for unrelated repositories or meeting-data queries.
Original author description
Execute Anarlog work immediately while recording issues, decisions, progress, and lessons in Linear. Use for Anarlog repository or Anarlog desktop, web, mobile, and API work, including related worktrees and ANLG issues. Explicit brainstorming stays discussion-first. Do not use for unrelated repositories or meeting-data queries.
How it works
- Start work immediately
- Record everything
- Record lessons as you go
SKILL.md preview
--- name: anarlog-workflow description: Execute Anarlog work immediately while recording issues, decisions, progress, and lessons in Linear. Use for Anarlog repository or Anarlog desktop, web, mobile, and API work, including related worktrees and ANLG issues. Explicit brainstorming stays discussion-first. Do not use for unrelated repositories or meeting-data queries. --- # Anarlog workflow Apply to Anarlog repository or Anarlog desktop, web, mobile, and API work. Apply the same workflow in other checkouts and worktrees. Linear is the system of record. Chat and the repo are not the archive. - Team: **Anarlog** (`ANLG`). - Workspace: [fastrepl-inc](https://linear.app/fastrepl-inc). - [Agent lessons](https://linear.app/fastrepl-inc/document/agent-lessons-45018045d01e). ## Start work immediately 1. Default to execution. When the user requests a change, reports a bug, or scopes work, start investigating and implementing immediately and carry it through to completion. Recording it in Linear is part of the work, not the deliverable or a reason to stop. 2. Only use a discussion-first workflow when the user explicitly asks for brainstorming, exploration of ideas, or planning without implementation. Answer informational questions directly. 3. Search Linear issues, documents, and comments for the topic, IDs (`ANLG-123`), and nearby decisions alongside execution. Read matching issues/docs and the team's **Agent lessons** early enough to inform relevant implementation decisions. Do not make this pass a prerequisite for starting useful work. 4. Reuse an existing issue when one fits. Create one only when nothing covers the work, on the right team, attached to the existing Linear project when one already tracks that surface. Keep the issue current as work proceeds; do not stop after creating or updating it. 5. If Linear is unavailable, continue authorized work and report the recording gap. Existing approval requirements for external actions and shared history still apply. ## Record everything - Work lives on a Linear issue. If the user states a decision, files a bug, or scopes new work, write it to Linear in the same turn. - Progress, decisions, blockers, and handoffs go on that issue as comments. - Durable specs, research, and product context go in Linear documents on the team or project. - Link the issue in commits/PRs when one exists (`ANLG-123`). ## Record lessons as you go A lesson is anything the next agent would otherwise rediscover: a failed approach, a non-obvious constraint, an architectural decision, a prod/debug gotcha, or a corrected assumption. - Write it immediately. Do not wait for a wrap-up. - Ticket-specific: comment on the issue under `## Lesson`. - Reusable across tickets: append to that team's **Agent lessons** document (create it if missing). Newest first: date, one-line title, what we learned, what to do next time. - Do not dump routine status into lessons. Do not leave important context only in the chat.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · modem-dev/ossrules | 90 | MIT |
| fastrepl/anarlog | 90 | MIT |
Database snapshot: 13.11.2026 · package version 4a3b10834a7e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100anarlog-webhooks
Receive and verify Anarlog webhooks. Use when setting up Anarlog webhook handlers, debugging x-anarlog-signature verification, or handling meeting.completed and note.enhanced events from the Anarlog meeting notes app. - 90anarlog
Query Anarlog meetings, notes, summaries, transcripts, participants, action items, and recurring history, or import a local recording. Use when a user asks about their Anarlog meeting data or needs meeting context for another task. - 85anarlog
Query Anarlog meetings, notes, summaries, transcripts, participants, action items, and recurring history, or import a local recording. Use when a user asks about their Anarlog meeting data or needs meeting context for another task. - 100linear-common-errors
Diagnose and fix common Linear API errors. Use when encountering Linear API errors, debugging integration issues, or troubleshooting authentication problems. Trigger with phrases like "linear error", "linear API error", "debug linear", "linear not working", "linear authentication error". - 100linear-issue-worker
Execute code tasks from Linear sub-issues: resolve dependencies, implement changes, validate Done Criteria, and sync status. Use when asked to work on, implement, or start coding a Linear issue (e.g. PRI-42). - 100linear-core-workflow-a
Issue lifecycle management with Linear: create, update, and transition issues. Use when implementing issue CRUD operations, state transitions, or building issue management features. Trigger with phrases like "linear issue workflow", "linear issue lifecycle", "create linear…