docs: issue 0016 — skill implementation workflow grill

Produces docs/notes/skill-implementation-workflow.md with agreed conventions
for all Chunk 3 skill issues (0017–0028). Key decisions:

- Per-skill process: source discovery (sub-agent) → source review with
  licence/security check (sub-agent) → conflict check vs constitution +
  factory principles (sub-agent) → synthesis grill → co-write iteratively
- Bootstrap: write-eval (hand-written) → write-skill (hand-written) →
  write-docs (first factory-authored, phase 2 of 0018) → everything else
- Upstream review changed from per-chunk-start to per-skill
- `when:` and `references:` frontmatter fields added to authoring standard
- Sub-agent usage prescribed as named steps in the workflow
- HITL: human reviewed and approved conventions

Updates: PRD implementation decisions; issues 0016–0028 with specific
acceptance criteria; docs/spec/overview.md; ROADMAP Chunk 3 housekeeping note
(bootstrap order, cadence, acceptance criteria status); CONTEXT.md Source field
(per-skill cadence, references: companion field); LESSONS.md with three patterns
from the grill session.

Post-grill additions (same session): Step 6 (session handoff) added to the
workflow; handoff section appended to issue 0016; handoff checklist item added
to Chunk 3 closure issue (0028).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

docs/issues/0016-skill-workflow-grill.md

@@ -21,11 +21,30 @@ HITL: requires human participation in the grill session.
 
 ## Acceptance criteria
 
-- [ ] Grill session completed covering all topics above
-- [ ] `docs/notes/skill-implementation-workflow.md` written with the agreed working conventions
-- [ ] `docs/prd/chunk-3-skills-library.md` updated with any decisions that change or extend the Implementation Decisions section
-- [ ] Issues 0017–0028 updated with specific acceptance criteria derived from the grill output
-- [ ] **HITL:** human participates in grill, reviews conventions, and approves before implementation of any skill begins
+- [x] Grill session completed covering all topics above
+- [x] `docs/notes/skill-implementation-workflow.md` written with the agreed working conventions
+- [x] `docs/prd/chunk-3-skills-library.md` updated with any decisions that change or extend the Implementation Decisions section
+- [x] Issues 0017–0028 updated with specific acceptance criteria derived from the grill output
+- [x] **HITL:** human participates in grill, reviews conventions, and approves before implementation of any skill begins
+
+## Handoff
+
+**Status:** complete  
+**Files produced:**
+- `docs/notes/skill-implementation-workflow.md`
+
+**Key decisions:**
+- Step 6 (session handoff) added post-grill: each skill session closes by appending a `## Handoff` section to the skill's issue file. Cross-cutting observations go to `LESSONS.md` immediately, not batched to chunk end.
+- Handoff artifact is the issue file, not a separate `docs/notes/` file — avoids proliferating per-skill note files.
+
+**Open threads:**
+- `when:` full bidirectional reference convention — deferred to Chunk 4
+- PRD/issue template scope — refined during 0019/0020 implementation
+- Merging `zoom-out` into architect role — revisit at Chunk 5 grill
+
+**Next session start:**
+- Load: `CONTEXT.md`, `docs/notes/skill-implementation-workflow.md`, issue 0017 or 0018
+- First action: Step 1 (source discovery) for `write-eval`
 
 ## Blocked by
 

docs/issues/0017-factory-write-eval.md

@@ -16,7 +16,7 @@ Build `write-eval` — the first factory meta-skill, bootstrapped with a hand-wr
 - For this first issue: write-eval's own eval is hand-crafted (write-eval cannot produce its own eval before it exists)
 - Origin: new skill; `source:` field populated only if upstream content is adopted (determine during implementation)
 
-Process: upstream review → trigger description written and tested first → skill body → hand-write eval → behavioral test.
+Process: follow `docs/notes/skill-implementation-workflow.md`. Bootstrap exception: steps 1–3 (source discovery, source review, conflict check) still apply; SKILL.md and eval.yaml are hand-written rather than factory-produced.
 
 ## Implementation notes
 
@@ -37,7 +37,14 @@ write-eval has no direct Pocock equivalent. Expect to synthesize from multiple u
 - [ ] `install.sh` deploys `write-eval` to `~/.agents/skills/` (confirm idempotent re-run)
 - [ ] **HITL:** human runs fresh-session behavioral test: invoke "write evals for this skill" and verify correct eval.yaml structure is produced
 - [ ] **HITL:** human reviews hand-written eval.yaml for correctness before committing
-- [ ] _(Further criteria to be refined after issue 0016 grill session)_
+- [ ] Per-skill process followed: source discovery (sub-agent) → source review with licence/security check (sub-agent) → conflict check against constitution + factory principles (sub-agent) → synthesis grill → co-write iteratively
+- [ ] Trigger description tested against explicit, implicit, and negative queries before body was written
+- [ ] `when:` frontmatter field present
+- [ ] `source:` field present only if upstream content adopted; absent if self-authored
+- [ ] `references:` field present if external citations used; absent otherwise
+- [ ] eval.yaml contains all 5 required test types: explicit trigger, implicit trigger, negative trigger, ≥2 deterministic output, ≥1 LLM-rubric quality
+- [ ] Body ≤500 lines; XML tags used only if ≥3 logical sections and 500+ tokens
+- [ ] `docs/spec/overview.md` updated to reflect `write-eval` deployed
 
 ## Blocked by
 

docs/issues/0018-factory-write-skill.md

@@ -5,19 +5,31 @@
 
 ## What to build
 
-Build `write-skill` — the second bootstrap skill, immediately after `write-eval`. Once `write-skill` exists, it is used to author all subsequent SKILL.md files in Chunk 3 rather than writing them by hand.
+### Phase 1: `write-skill`
+
+Build `write-skill` — the second bootstrap skill. Once complete, it is used to author all subsequent SKILL.md files in Chunk 3.
 
 **Trigger description** (from skills index): "Write a new skill for X, create a SKILL.md that does Y"
 
 **Key constraints:**
-- Produces a complete SKILL.md following the authoring standard (frontmatter, role, when/when-not, required inputs, constraints, process, output format, failure handling)
-- Validates trigger description against three test queries (explicit, implicit, negative) before completing
+- Produces a complete SKILL.md following the authoring standard in `docs/notes/skill-implementation-workflow.md`
+- Validates trigger description against explicit, implicit, and negative test queries before completing
 - Flags if the proposed skill overlaps with an existing skill in the library
 - Skill file: `.agents/skills/write-skill/SKILL.md`; `metadata.category: factory`
-- Origin: new skill (check upstream for prior art during implementation); `source:` populated only if upstream content is adopted
+- SKILL.md is hand-written (write-skill cannot author itself before it exists)
 - Eval via `write-eval` (issue 0017)
 
-Process: upstream review → trigger-first → skill body → `write-eval` for eval.yaml → behavioral test.
+### Phase 2: `write-docs`
+
+Build `write-docs` — the first skill authored via `write-skill` itself (the factory eating itself for the first time). Implement immediately after phase 1 is complete and deployed.
+
+**Trigger description** (from skills index): "Write documentation for X, document this module, create docs for this feature"
+
+**Key constraints:**
+- Skill file: `.agents/skills/write-docs/SKILL.md`; `metadata.category: implement`
+- SKILL.md authored via `write-skill`; eval via `write-eval`
+- Follow full per-skill workflow from `docs/notes/skill-implementation-workflow.md` (sub-agents for discovery, review, conflict check)
+- Derives from code and spec; never invents behaviour
 
 ## Implementation notes
 
@@ -36,7 +48,14 @@ Follow the per-skill workflow defined in `docs/notes/skill-implementation-workfl
 - [ ] `install.sh` deploys `write-skill` to `~/.agents/skills/`
 - [ ] **HITL:** human runs behavioral test: invoke "write a new skill for X" and verify the produced SKILL.md meets the authoring standard
 - [ ] **HITL:** human reviews SKILL.md and eval before committing
-- [ ] _(Further criteria to be refined after issue 0016 grill session)_
+- [ ] Per-skill process followed for both phases (see `docs/notes/skill-implementation-workflow.md`)
+- [ ] Trigger description for each skill tested against explicit, implicit, and negative queries before body written
+- [ ] `when:` frontmatter field present in both SKILL.md files
+- [ ] `source:` and `references:` fields correctly populated or absent
+- [ ] eval.yaml for each skill contains all 5 required test types
+- [ ] Body ≤500 lines for each skill
+- [ ] Phase 2 (`write-docs`) is the first skill produced end-to-end by the factory
+- [ ] `docs/spec/overview.md` updated to reflect both skills deployed
 
 ## Blocked by
 

docs/issues/0019-factory-skills-remaining.md

@@ -7,7 +7,7 @@
 
 The remaining 5 factory meta-skills, authored using `write-skill` (0018). `write-adr` must be implemented first within this group — it is called by `design/grill-me` (issue 0020). All skills in this group are new.
 
-Each skill follows the per-skill workflow from issue 0016: upstream review → trigger-first → `write-skill` to author SKILL.md → `write-eval` to produce eval → behavioral test.
+Each skill follows the per-skill workflow from `docs/notes/skill-implementation-workflow.md`. `write-adr` must be verified before starting issue 0020.
 
 **Skills and trigger descriptions** (from skills index):
 
@@ -46,7 +46,14 @@ For all skills in this group: these are meta-skills with no direct Pocock placeh
 - [ ] `install.sh` deploys all 5 to `~/.agents/skills/`
 - [ ] **HITL:** human runs behavioral test per skill; output format matches constraints
 - [ ] **HITL:** human reviews each SKILL.md and eval before committing
-- [ ] _(Further criteria to be refined after issue 0016 grill session)_
+- [ ] Per-skill process followed for all 5 skills: source discovery (sub-agent) → source review with licence/security check (sub-agent) → conflict check against constitution + factory principles (sub-agent) → synthesis grill → co-write iteratively
+- [ ] Trigger description for each skill tested against explicit, implicit, and negative queries before body written
+- [ ] `when:` frontmatter field present in all SKILL.md files
+- [ ] `source:` and `references:` fields correctly populated or absent
+- [ ] eval.yaml for each skill contains all 5 required test types
+- [ ] Body ≤500 lines for each skill
+- [ ] `write-adr` implemented and passing behavioral test before design skills issue (0020) begins
+- [ ] `docs/spec/overview.md` updated to reflect all 5 skills deployed
 
 ## Blocked by
 

docs/issues/0020-design-skills.md

@@ -30,7 +30,7 @@ The 6 design phase skills. Four are refactors of existing Pocock placeholders; t
 
 ## Implementation notes
 
-Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md` (produced by issue 0016).
+Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md`.
 
 **Known upstream sources to review for this category:**
 - `mattpocock/skills` — original `grill-me`, `to-prd`, `to-issues`, `grill-with-docs` placeholders; review at current HEAD for improvements; record SHAs in `source:` for refactored skills
@@ -51,7 +51,14 @@ For new skills (`architecture-review`, `grill-lean`): search for prior art in th
 - [ ] `install.sh` deploys all 6 to `~/.agents/skills/`
 - [ ] **HITL:** human runs behavioral test per skill; output meets constraints
 - [ ] **HITL:** human reviews each SKILL.md and eval before committing
-- [ ] _(Further criteria to be refined after issue 0016 grill session)_
+- [ ] Per-skill process followed for all 6 skills: source discovery (sub-agent) → source review with licence/security check (sub-agent) → conflict check against constitution + factory principles (sub-agent) → synthesis grill → co-write iteratively
+- [ ] Trigger description for each skill tested against explicit, implicit, and negative queries before body written
+- [ ] `when:` frontmatter field present in all SKILL.md files
+- [ ] `source:` fields populated for all refactored Pocock skills; `references:` present if external citations used
+- [ ] eval.yaml for each skill contains all 5 required test types
+- [ ] Body ≤500 lines for each skill
+- [ ] Conflict check run against constitution before synthesis grill; no unresolved HITL or data classification violations
+- [ ] `docs/spec/overview.md` updated to reflect all 6 skills deployed
 
 ## Blocked by
 

docs/issues/0021-implement-skills.md

@@ -1,11 +1,11 @@
-# 0021 — Implement skills: implement-feature, tdd, refactor, write-docs, diagnose
+# 0021 — Implement skills: implement-feature, tdd, refactor, diagnose
 
 **Type:** HITL  
 **Parent PRD:** `docs/prd/chunk-3-skills-library.md`
 
 ## What to build
 
-The 5 implement phase skills. Two are new; three are preserved Pocock placeholders upgraded to the authoring standard. All authored via `write-skill` (0018), evals via `write-eval` (0017).
+The 4 implement phase skills. One is new; three are preserved Pocock placeholders upgraded to the authoring standard. All authored via `write-skill` (0018), evals via `write-eval` (0017). `write-docs` has been moved to issue 0018 phase 2.
 
 **Skills, origins, and trigger descriptions:**
 
@@ -14,19 +14,17 @@ The 5 implement phase skills. Two are new; three are preserved Pocock placeholde
 | `implement-feature` | New | Implement a feature, build this, write the code for X |
 | `tdd` | Preserved; frontmatter + standard added | TDD, test-driven, red-green-refactor |
 | `refactor` | New | Refactor this code, improve structure, clean up |
-| `write-docs` | New | Write documentation, add docstrings, generate README |
 | `diagnose` | Preserved; frontmatter + standard added | Diagnose this, what's wrong with X, debug this |
 
 **Key constraints per skill:**
 - `implement-feature`: must start from a linked issue with an EARS spec (checks `docs/issues/` in the file-based phase, Gitea MCP when configured); flags if none exists; no unrequested abstractions; updates `docs/spec/` as part of implementation if behaviour changes; calls `tdd` as its implementation methodology
 - `tdd`: composable and separate from `implement-feature` so TDD can be used outside full feature implementation; red-green-refactor loop
 - `refactor`: preserves all existing behaviour; documents what changed and why
-- `write-docs`: derives from code and spec; never invents behaviour
 - `diagnose`: preserved behavior; add frontmatter, authoring standard sections, and dead-reference cleanup
 
 ## Implementation notes
 
-Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md` (produced by issue 0016).
+Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md`.
 
 **Known upstream sources to review for this category:**
 - `mattpocock/skills` — original `tdd` and `diagnose` placeholders; review at current HEAD; record SHAs in `source:` for any adopted content
@@ -36,15 +34,22 @@ For new skills (`implement-feature`, `refactor`, `write-docs`): search for prior
 
 ## Acceptance criteria
 
-- [ ] All 5 SKILL.md files exist at `.agents/skills/<skill-name>/SKILL.md`; `metadata.category: implement`; authoring standard met
+- [ ] All 4 SKILL.md files exist at `.agents/skills/<skill-name>/SKILL.md`; `metadata.category: implement`; authoring standard met (`write-docs` is in issue 0018 phase 2)
 - [ ] Dead references removed from Pocock skills (`tdd`, `diagnose`)
 - [ ] `implement-feature` checks for linked issue with EARS spec before proceeding; calls `tdd` by name
 - [ ] `source:` fields populated for adopted upstream content
 - [ ] Each skill has a co-located eval at `.agents/evals/implement/<skill-name>/eval.yaml` via `write-eval`
-- [ ] `install.sh` deploys all 5 to `~/.agents/skills/`
+- [ ] `install.sh` deploys all 4 to `~/.agents/skills/`
 - [ ] **HITL:** human runs behavioral test per skill
 - [ ] **HITL:** human reviews each SKILL.md and eval before committing
-- [ ] _(Further criteria to be refined after issue 0016 grill session)_
+- [ ] Per-skill process followed for all 4 skills: source discovery (sub-agent) → source review with licence/security check (sub-agent) → conflict check against constitution + factory principles (sub-agent) → synthesis grill → co-write iteratively
+- [ ] Trigger description for each skill tested against explicit, implicit, and negative queries before body written
+- [ ] `when:` frontmatter field present in all SKILL.md files
+- [ ] `source:` and `references:` fields correctly populated or absent
+- [ ] eval.yaml for each skill contains all 5 required test types
+- [ ] Body ≤500 lines for each skill
+- [ ] `write-docs` confirmed removed from scope (implemented in issue 0018 phase 2)
+- [ ] `docs/spec/overview.md` updated to reflect all 4 skills deployed
 
 ## Blocked by
 

docs/issues/0022-test-skills.md

@@ -22,7 +22,7 @@ The 3 test phase skills. All are new. Authored via `write-skill` (0018), evals v
 
 ## Implementation notes
 
-Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md` (produced by issue 0016).
+Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md`.
 
 **Known upstream sources to review:**
 - `mattpocock/skills` — check for any test-phase skills in the current set
@@ -39,7 +39,13 @@ Follow the per-skill workflow defined in `docs/notes/skill-implementation-workfl
 - [ ] `install.sh` deploys all 3 to `~/.agents/skills/`
 - [ ] **HITL:** human runs behavioral test per skill
 - [ ] **HITL:** human reviews each SKILL.md and eval before committing
-- [ ] _(Further criteria to be refined after issue 0016 grill session)_
+- [ ] Per-skill process followed for all 3 skills: source discovery (sub-agent) → source review with licence/security check (sub-agent) → conflict check against constitution + factory principles (sub-agent) → synthesis grill → co-write iteratively
+- [ ] Trigger description for each skill tested against explicit, implicit, and negative queries before body written
+- [ ] `when:` frontmatter field present in all SKILL.md files
+- [ ] `source:` and `references:` fields correctly populated or absent
+- [ ] eval.yaml for each skill contains all 5 required test types
+- [ ] Body ≤500 lines for each skill
+- [ ] `docs/spec/overview.md` updated to reflect all 3 skills deployed
 
 ## Blocked by
 

docs/issues/0023-review-skills.md

@@ -29,7 +29,7 @@ The 4 review phase skills plus the `cliff.toml` changelog config. All skills are
 
 ## Implementation notes
 
-Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md` (produced by issue 0016).
+Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md`.
 
 **Known upstream sources to review:**
 - `mattpocock/skills` — check for code-review or security-review skills
@@ -49,7 +49,13 @@ Follow the per-skill workflow defined in `docs/notes/skill-implementation-workfl
 - [ ] `install.sh` deploys all 4 skills to `~/.agents/skills/`
 - [ ] **HITL:** human runs behavioral test per skill
 - [ ] **HITL:** human reviews each SKILL.md, eval, and cliff.toml before committing
-- [ ] _(Further criteria to be refined after issue 0016 grill session)_
+- [ ] Per-skill process followed for all 4 skills: source discovery (sub-agent) → source review with licence/security check (sub-agent) → conflict check against constitution + factory principles (sub-agent) → synthesis grill → co-write iteratively
+- [ ] Trigger description for each skill tested against explicit, implicit, and negative queries before body written
+- [ ] `when:` frontmatter field present in all SKILL.md files
+- [ ] `source:` and `references:` fields correctly populated or absent
+- [ ] eval.yaml for each skill contains all 5 required test types
+- [ ] Body ≤500 lines for each skill
+- [ ] `docs/spec/overview.md` updated to reflect all 4 skills deployed
 
 ## Blocked by
 

docs/issues/0024-deploy-skills.md

@@ -24,7 +24,7 @@ The 4 deploy phase skills. All are new. Authored via `write-skill` (0018), evals
 
 ## Implementation notes
 
-Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md` (produced by issue 0016).
+Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md`.
 
 **Known upstream sources to review:**
 - `bmad-method/bmad-method` — BMAD ops/deploy patterns and deployment checklist approach
@@ -41,7 +41,13 @@ Follow the per-skill workflow defined in `docs/notes/skill-implementation-workfl
 - [ ] `install.sh` deploys all 4 to `~/.agents/skills/`
 - [ ] **HITL:** human runs behavioral test per skill
 - [ ] **HITL:** human reviews each SKILL.md and eval before committing
-- [ ] _(Further criteria to be refined after issue 0016 grill session)_
+- [ ] Per-skill process followed for all 4 skills: source discovery (sub-agent) → source review with licence/security check (sub-agent) → conflict check against constitution + factory principles (sub-agent) → synthesis grill → co-write iteratively
+- [ ] Trigger description for each skill tested against explicit, implicit, and negative queries before body written
+- [ ] `when:` frontmatter field present in all SKILL.md files
+- [ ] `source:` and `references:` fields correctly populated or absent
+- [ ] eval.yaml for each skill contains all 5 required test types
+- [ ] Body ≤500 lines for each skill
+- [ ] `docs/spec/overview.md` updated to reflect all 4 skills deployed
 
 ## Blocked by
 

docs/issues/0025-operate-skills.md

@@ -24,7 +24,7 @@ The 4 operate phase skills. All are new. Authored via `write-skill` (0018), eval
 
 ## Implementation notes
 
-Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md` (produced by issue 0016).
+Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md`.
 
 **Known upstream sources to review:**
 - `bmad-method/bmad-method` — BMAD ops role patterns
@@ -42,7 +42,13 @@ Follow the per-skill workflow defined in `docs/notes/skill-implementation-workfl
 - [ ] `install.sh` deploys all 4 to `~/.agents/skills/`
 - [ ] **HITL:** human runs behavioral test per skill
 - [ ] **HITL:** human reviews each SKILL.md and eval before committing
-- [ ] _(Further criteria to be refined after issue 0016 grill session)_
+- [ ] Per-skill process followed for all 4 skills: source discovery (sub-agent) → source review with licence/security check (sub-agent) → conflict check against constitution + factory principles (sub-agent) → synthesis grill → co-write iteratively
+- [ ] Trigger description for each skill tested against explicit, implicit, and negative queries before body written
+- [ ] `when:` frontmatter field present in all SKILL.md files
+- [ ] `source:` and `references:` fields correctly populated or absent
+- [ ] eval.yaml for each skill contains all 5 required test types
+- [ ] Body ≤500 lines for each skill
+- [ ] `docs/spec/overview.md` updated to reflect all 4 skills deployed
 
 ## Blocked by
 

docs/issues/0026-iac-skills.md

@@ -20,7 +20,7 @@ The 2 IaC domain skills scoped for Chunk 3. Both are new. The 5 deferred IaC ski
 
 ## Implementation notes
 
-Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md` (produced by issue 0016).
+Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md`.
 
 **Known upstream sources to review:**
 - Search GitHub and agentskills.io for open-source Docker Compose and IaC security review skills
@@ -37,7 +37,13 @@ Follow the per-skill workflow defined in `docs/notes/skill-implementation-workfl
 - [ ] `install.sh` deploys both to `~/.agents/skills/`
 - [ ] **HITL:** human runs behavioral test per skill
 - [ ] **HITL:** human reviews each SKILL.md and eval before committing
-- [ ] _(Further criteria to be refined after issue 0016 grill session)_
+- [ ] Per-skill process followed for both skills: source discovery (sub-agent) → source review with licence/security check (sub-agent) → conflict check against constitution + factory principles (sub-agent) → synthesis grill → co-write iteratively
+- [ ] Trigger description for each skill tested against explicit, implicit, and negative queries before body written
+- [ ] `when:` frontmatter field present in both SKILL.md files
+- [ ] `source:` and `references:` fields correctly populated or absent
+- [ ] eval.yaml for each skill contains all 5 required test types
+- [ ] Body ≤500 lines for each skill
+- [ ] `docs/spec/overview.md` updated to reflect both skills deployed
 
 ## Blocked by
 

docs/issues/0027-cross-cutting-skills.md

@@ -29,7 +29,7 @@ The 7 cross-cutting skills (no single phase home). Three are new; four are prese
 
 ## Implementation notes
 
-Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md` (produced by issue 0016).
+Follow the per-skill workflow defined in `docs/notes/skill-implementation-workflow.md`.
 
 **Known upstream sources to review:**
 - `mattpocock/skills` — original `improve-codebase-architecture`, `triage`, `zoom-out`, `caveman` placeholders; record SHAs for adopted content
@@ -47,7 +47,13 @@ Follow the per-skill workflow defined in `docs/notes/skill-implementation-workfl
 - [ ] `install.sh` deploys all 7 to `~/.agents/skills/`
 - [ ] **HITL:** human runs behavioral test for each new/refactored skill
 - [ ] **HITL:** human reviews each SKILL.md and eval before committing
-- [ ] _(Further criteria to be refined after issue 0016 grill session)_
+- [ ] Per-skill process followed for all new/refactored skills: source discovery (sub-agent) → source review with licence/security check (sub-agent) → conflict check against constitution + factory principles (sub-agent) → synthesis grill → co-write iteratively
+- [ ] Trigger description for each skill tested against explicit, implicit, and negative queries before body written
+- [ ] `when:` frontmatter field present in all new/refactored SKILL.md files (`caveman` exempt)
+- [ ] `source:` and `references:` fields correctly populated or absent
+- [ ] eval.yaml for each new/refactored skill contains all 5 required test types (`caveman` exempt)
+- [ ] Body ≤500 lines for each skill
+- [ ] `docs/spec/overview.md` updated to reflect all skills deployed
 
 ## Blocked by
 

docs/issues/0028-chunk-3-closure.md

@@ -17,6 +17,7 @@ Close out Chunk 3 once all 42 skills are complete: update the skills index to re
 **Behavioral test scope:** All 42 skills (including `write-eval`, `write-skill`, and the 4 preserved skills). The `caveman` skill is exempt — it has no content-generating behavior to verify.
 
 **LESSONS.md:** Extract any cross-session learnings from Chunk 3 implementation and add entries per the LESSONS.md format. Three or more observations on the same pattern graduate to the relevant standing file.
+6. Review `docs/notes/skill-implementation-workflow.md` — verify the conventions are still accurate; update any entries that changed during implementation.
 
 ## Acceptance criteria
 
@@ -26,6 +27,8 @@ Close out Chunk 3 once all 42 skills are complete: update the skills index to re
 - [ ] `docs/ROADMAP.md` Chunk 3 row updated to ✅
 - [ ] Behavioral test run completed; all skills pass their trigger test; failures documented as issues for resolution
 - [ ] `LESSONS.md` updated with Chunk 3 observations
+- [ ] `docs/notes/skill-implementation-workflow.md` reviewed and updated to reflect any workflow changes discovered during Chunk 3
+- [ ] All skill issues (0017–0027) have a `## Handoff` section with status `complete`
 - [ ] **HITL:** human verifies the complete skills library in a fresh session before marking Chunk 3 done
 
 ## Blocked by