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>
2.8 KiB
2.8 KiB
0016 — Second grill: skill implementation workflow
Type: HITL
Parent PRD: docs/prd/chunk-3-skills-library.md
What to build
Run a dedicated grill session on the general skill implementation workflow before any skill is written. The PRD identifies this as the first issue after the AGENTS.md prerequisite — the grill produces the working conventions applied to all subsequent skill issues (0017–0028).
The grill covers:
- Per-skill process steps: trigger-first, eval-first, upstream review, source: field population
- How the
factory/write-eval-first bootstrap works in practice (hand-written eval for write-eval itself; write-eval used for all subsequent skills) - Working conventions for refactors (existing Pocock skills) vs new skills
- How to handle a skill that combines patterns from multiple upstream sources
- The upstream review process at chunk start: what to check, what to record, how to decide whether to pull changes in
- Any open questions from the PRD flagged as "refine during implementation" (PRD/issue template scope, bidirectional reference convention in skill frontmatter)
Output is documented in docs/notes/skill-implementation-workflow.md, used to update docs/prd/chunk-3-skills-library.md with any decisions made, and used to refine issues 0017–0028 with specific acceptance criteria.
HITL: requires human participation in the grill session.
Acceptance criteria
- Grill session completed covering all topics above
docs/notes/skill-implementation-workflow.mdwritten with the agreed working conventionsdocs/prd/chunk-3-skills-library.mdupdated 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
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
## Handoffsection to the skill's issue file. Cross-cutting observations go toLESSONS.mdimmediately, 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-outinto 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
- 0015 (AGENTS.md refactor must be complete so grill references stable file structure)