Skill: Iteration (Human Responsibility + V2 Plan)
Purpose
Generate:
- •the Human Responsibility file (what must be explicitly declared/owned by humans), and
- •a practical V2 implementation plan (including deltas vs prior plans where present).
Inputs
Required inputs:
- •Skill outputs 1–8 (and 9 if re-running)
- •Unioned unknowns from prior skills
- •Templates:
- •
data/responsibility_template.md - •
data/planning_template.md
- •
- •Optional
human_declarations(only if provided; do not invent) - •IR evidence index (for evidence ids)
Outputs
- •Human Responsibility file (template-populated)
- •V2 plan (template-populated)
- •Delta summary if a prior plan exists (kept/changed/removed with reasons)
Rules
Evidence & uncertainty (non-negotiable)
- •Do not “resolve” unknowns by inference. Only close unknowns via explicit human declarations if provided.
- •Use IR evidence ids for evidence_used where applicable.
Human responsibility strictness
- •Ensure the Human Responsibility file includes required markers and placeholders.
- •Group unknowns by document section, and label each as blocking or non-blocking.
- •For each required human declaration, specify:
- •owner role (not a person name)
- •question
- •why it matters
- •acceptable answer format
- •blocking / not blocking
- •suggested deadline
Plan realism
- •Include effort sizing (S/M/L) and dependencies between work items.
- •Split “can ship now” vs “requires declarations/inputs” explicitly.
- •If a prior plan exists, include a delta summary with rationale tied to new evidence or risk tier outputs.
System Prompt
You are a program manager for model governance. Produce a practical, auditable plan that a team can execute.
User Prompt Template
Using templates and prior outputs:
- •Draft the Human Responsibility file, enumerating required human declarations and owners.
- •Draft the V2 plan with workstreams, dependencies, and sizing.
- •If an older plan exists, provide a delta summary (kept/changed/removed) with reasons.
Post-run Checks
- •Human Responsibility includes all required markers/placeholders from the template.
- •Unknowns are grouped, labeled blocking/non-blocking, and assigned an owner role.
- •Plan includes sizing, dependencies, and a clear “ship now vs later” split.