CI System Design — Talent Factory

CI System Design — Talent Factory

Author: Pablo (Production Line Architect) Date: 2026-03-21 Status: Design (not yet implemented) Resolves: CI-0001, CI-0005, CI-0007, CI-0010

1. Feedback Capture (CI-0005)

A /ci slash command in the talent-factory workspace. Accepts a one-liner description and optional flags:

/ci "WO template missing AI platform field" --category wo-template --priority high

Behavior: auto-appends a row to company/factory-backlog.md with date, source (caller context), category, and status=Open. If --category is omitted, the command infers it from keywords. No approval gate on capture — triage happens downstream.

Two additional capture paths feed the same backlog:

  • Fiona's feedback analysis — product/client items surfaced during 30/60/90 reviews.
  • Direct edit — any factory worker can append a row manually for quick fixes.

2. Triage Ownership (CI-0010)

Stream Owner Scope
Product improvements Fiona -> Max Client bugs, skill refinements, deployed talent issues
Factory process Pablo WO template, pipeline stages, assembly process, patterns
Client relationship Dana Communication channels, delivery logistics, billing

Rule: Fiona triages everything she surfaces. Factory workers who log items via /ci self-assign a category; Pablo reviews unassigned items at cadence.

3. Lessons per Skill (CI-0007)

Decision: Option A — companion file.

Pattern: {skill-name}.lessons.md alongside the skill file.

Rationale:

  • Skills are already self-contained units shipped to client repos. Embedding lessons (Option B) pollutes the deliverable. A central file (Option C) creates merge friction when multiple skills evolve in parallel.
  • Companion files travel with the skill during copy/clone but can be excluded from client delivery via .gitignore or the deploy stage filter.
  • Format: flat list, newest first, each entry tagged with date and source (backlog ID or session).
## 2026-03-18 — CI-0004
WO-001 delivery: /ea-exigences-note-revue generated empty sections when input had no stakeholders.
Action: added guard clause + default text.

4. Cadence

Event Frequency Participants Purpose
Capture Continuous Any factory worker Log items via /ci or direct edit
Triage Weekly Pablo + Fiona Categorize, assign, prioritize new items
Review Per production run kickoff Pablo + relevant build team Scan backlog for items that affect the upcoming build
Retrospective End of each delivery (post-Stage 9) Full delivery team Harvest lessons, bulk-log to backlog

This is a hybrid of Q3 Options B and C from the design brief: a light weekly triage plus a production-run-triggered deeper review.

5. Flow

CAPTURE ──> TRIAGE ──> ASSIGN ──> IMPLEMENT ──> VERIFY ──> CLOSE
  /ci        weekly     owner      normal dev    Quinn/     mark
  Fiona      Pablo+     sets       or next       peer       Closed in
  direct     Fiona      status     prod run      review     backlog
             assign     to WIP
             category

Status values: Open -> Triaged -> WIP -> Verify -> Closed

Blocked items get a Blocked-by: CI-XXX note. Items that spawn decisions get a TFD reference.

6. Integration with Production Line

The CI system feeds back into the digital-talent production line at three points:

  1. Templates — WO template and skill template updates (CI-0002, CI-0003) are applied to production-lines/digital-talent/templates/ and take effect on the next Type 1/2 build.
  2. Stage definitions — Process improvements modify stage docs in production-lines/digital-talent/stages/. Example: CI-0009 (interactive re-run) would update the QA gate stage.
  3. Lessons -> pattern catalog — Recurring lessons that affect multiple skills get promoted to pattern updates via Ada. The companion .lessons.md file is the source; Ada reviews at retrospective cadence.

No retroactive changes to already-deployed talents. Improvements apply forward only. Type 3 enhancement requests are the vehicle for pushing fixes to live deployments.

Next Steps

  1. CEO approves this design (or requests changes).
  2. Pablo implements /ci command (CI-0005).
  3. Pablo adds Triaged and WIP status columns to backlog format.
  4. Fiona confirms triage ownership split works for her workflow.