Aiwork Protocol

.aiwork Folder Protocol

Repository-local folder for AI work artifacts, organized by feature or task. Artifacts structure thinking in-session and provide context for future sessions when referenced manually.

Folder layout

.aiwork/
  2026-01-27_auth-refactor/
    intent.md
    triage.md
    spec.md

• Folder: {YYYY-MM-DD}_{slug}/, slug lowercase kebab-case, max 40 chars.
• File: {type}.md. Numbering for multiples of same type:
  • plan.md → plan_2.md → plan_3.md — when one plan was expected, more followed.
  • plan_1.md → plan_2.md → plan_3.md — when multiple are expected from the start.
  • Don't mix schemes in one folder.
• Multi-day: optionally prefix filenames with {YYYY-MM-DD}_.

Usually 1-2 artifacts per task. Pick types that fit.

Grouping and restructuring

One task = one folder. Drift signals:

• Two folders with overlapping scope or near-identical slugs
• Cross-folder references: / "Source plan: ../..." pointers
• Folder that exists only because a ticket number arrived mid-task

On drift, propose consolidation: move artifacts into the canonical folder with a superseded_by: pointer, or merge under one date. Ask before moving files.

A pointer to an epic's areas.md is not drift — it's a legitimate parent link (see below). Drift is two folders for the same task.

Epics

A folder is dated when its work starts and holds a few hours' to a few days' work. A big idea doesn't fit: months can pass between framing it and finishing the last piece.

So split it. The epic folder is an index, not a task: spec.md (or nothing, when the framing is short) plus areas.md. Each area later becomes a normal task folder, dated when it actually starts.

.aiwork/
  2026-06-09_kurzy-platforma/     # epic, framed in June
    spec.md
    areas.md
  2026-08-28_auth-layer/          # area 02, started in August
    spec.md
    tickets/

The presence of areas.md is what marks a folder as an epic. Its area entries carry the roll-up:

## 02 — Auth layer

**Status:** in-progress → `../2026-08-28_auth-layer/`

One line edited when an area starts, one when it's done. The area's own spec points back with the existing references: field ("Epic: ../2026-06-09_kurzy-platforma/areas.md") — no dedicated field for it.

Write each area's spec lazily, when its turn comes. Don't spec wave 4 during wave 1.

Artifact types (all optional)

• intent — what the originator wants, in their own words, before anyone decides how. A sentence is enough. Record what was said, without interviewing or exploring the codebase for it. Carries status (see below). /to-spec answers it
• triage — problem framing, what's known
• research — codebase exploration, doc reading
• prd — product requirements, success criteria
• spec — technical/architecture decisions
• areas — decomposition of an oversized spec into areas, each becoming its own task folder later: dependency graph, wave order, and per area its deliverables, what it depends on, how it's verified, and a status line (see Epics)
• plan — actionable implementation steps
• review — code review report. Carries reviewed_sha: in frontmatter, the commit the review actually read
• notes — findings, decisions from implementation
• implementation-notes — short log kept by /implement, for what the reader must act on. Work only a human can finish, anything left unverified, decisions taken where the spec was silent, deviations, contradicted assumptions, a stopped chain. Never what was built or tested. Many tickets warrant no entry.
• tickets/ — subfolder of vertical-slice tickets, one file per ticket (NN_slug.md, numbered in dependency order), status + blocked_by in frontmatter; created by /to-tickets, worked by /implement-spec (or /implement for a single ticket)
• docs/ — subfolder for downloaded external docs

Custom types (cascade-map.md, checklist.md) are fine when they fit better.

Division of labor with triage: both skills trigger on the word "triage". aiwork-protocol decides where the artifact lands; triage decides what goes in it. Producing the report content is triage's job — this skill only names and places the file.

When to create a new plan

New plan file when the approach changes or new constraints emerge between iterations. Otherwise continue the previous plan — don't start one just because the session is new.

Frontmatter

Folder date + filename already encode creation time and type, so don't duplicate. Add structured data that's useful for the artifact.

---
ticket: #123456
references:
  - "Parent: #38234"
  - https://docs.example.com/auth
story_points: 8
superseded_by: plan_2.md
---

Common fields: ticket, references, superseded_by. Avoid fields that need manual upkeep across sessions.

status on intent artifacts

proposed (an idea parked, not yet decided), accepted (going ahead), or declined (keep the file, the reasoning stays on record). /implement-spec stops on an intent that isn't accepted.

status on spec and plan artifacts

The one field worth the upkeep: without it a folder with no tickets/ is indistinguishable from a finished one. Set it on spec.md (or the current plan*.md when there is no spec) and update it as the work moves.

An absent status means unknown, not not-started — a task is split into tickets/ only when that is worth doing, so neither the missing field nor the missing tickets say anything about whether the work happened.

Folders that use tickets/ don't need it: ticket statuses already say where the work stands.

---
status: blocked
blocked_by: waiting on the payment-gateway contract
---

verified on tickets and specs

Records which passes ran on the code as it stood when the artifact reached done. A list of pass names; absent means nothing recorded. On a ticket, or on spec.md when there are no tickets.

verified: [checks, behaviour, review]

Whoever runs a pass appends its name. Passes that judge the whole result rather than one ticket, a UX walkthrough of a flow or a human acceptance, are usually their own ticket, so they land there.

These fields are evidence: the plugin's verified-gate hook holds the end of a turn when a ticket claims done without an on-app pass (behaviour, ux or human). Set them because the pass ran.

reviewed_sha on review artifacts

The commit the review was written against, full or abbreviated:

reviewed_sha: 4f2c1ab

The same hook holds a turn on a review with no sha, or one naming a commit unreachable from HEAD. Fixes after the review are expected; the sha is a starting point, not a claim that nothing moved since.

Version control

Whether to commit .aiwork/ is up to the project — either traceability or ephemeral working artifacts is fine.