← All craftbooks

Weekly Pipeline Review

Review and QAevalv1.0.0released 2026-06-05workflow: build-loop

The weekly walk of a job-search pipeline — a grounded snapshot of every application (what moved in the last seven days, what went stale, which follow-ups are due), then a review that chases or consciously parks every stalled item and commits to exactly three concrete priorities for next week. Built for the Job Hunt project's weekly cadence; also runs on demand whenever the pipeline feels foggy.

Steps

Entry step: snapshot. Each step names the specialist role it wants; the full working prompt is expandable.

  1. Snapshot the pipelineLoopbaancoachentry

    the grounded state: per-stage counts, movement, staleness, follow-ups due

    Show working prompt
    Ground the review in the real record — invent nothing. Step 1: read the live pipeline through the pipeline status capability on your current roster when available; otherwise read the workspace pipeline.json and activity.json records directly. Step 2: snapshot per-stage counts and list every application with its stage and last-touched date. Step 3: mark movement — anything whose stage changed in the last seven days. Step 4: mark staleness — any active application untouched for more than seven days. Step 5: list follow-ups due — logged follow-up events due within the next seven days or overdue. Step 6: note materials debt: serious applications missing a tailored résumé or company brief. Write the snapshot via write_task_note AND to notes/pipeline-snapshot.md.
  2. Write the weekly reviewLoopbaancoach

    moved, stalled with unblocking actions, follow-ups, and exactly three priorities

    Show working prompt
    Write reports/weekly-pipeline-review.md from the snapshot. Step 1: '## Moved this week' — each change in one line, celebrated where it deserves it. Step 2: '## Stalled' — every stale item with its unblocking action; the carry-over rule is absolute: each one is explicitly chased, consciously parked with a reason, or closed — nothing is silently dropped. Step 3: '## Follow-ups due' — who, about what, by when. Step 4: '## Materials debt' — tailoring and briefs owed for serious applications. Step 5: '## Next week' — EXACTLY three concrete priorities; three, not ten. Every line must trace to the snapshot. On a loop-back, fix ONLY the named issues.
  3. Evaluatereviewer

    Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.

    Show working prompt
    Audit the review against the snapshot. Step 1: cross-check — every application in the snapshot is accounted for in the review; FAIL any active application that appears in neither Moved, Stalled, nor Follow-ups. Step 2: check the carry-over rule — every stale item has an explicit chase, park-with-reason, or close. Step 3: count the next-week priorities — FAIL unless exactly three, each concrete enough to start tomorrow. Step 4: every follow-up line has a who, a what, and a when. Write PASS/FAIL per criterion.
    
    Then route — this is the whole point of the loop:
    
    - **Every criterion PASSES →** call `advance_task_step({ ref, stepId: "evaluate", next: "finish" })`.
    - **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: "evaluate", next: "review" })` to loop back. The builder fixes exactly those gaps.
    
    Never route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.
  4. Finishdeveloper

    All acceptance criteria met. Stamp a short summary and report DONE.

    Show working prompt
    Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.

Triggers

Phrases that suggest this craftbook to a crew.

Source

View this craftbook on GitHub · MIT license