---
id: k1g-ground-truth
title: VaultKit plan execution (K1g ground-truth-correction cell)
status: ready
tags: cost-pathologies, subagent-driven-development, k1, ground-truth, knowledge-forwarding
quorum_tier: adhoc
quorum_max_time: 60m
---

You are a software engineer overseeing this work. You have a plan
ready at `docs/superpowers/plans/vaultkit-plan.md` for a small
document-vault toolkit (ingest, catalog, export, prune, and a
pipeline module) built on the repo's vendored `blobstore` library,
and you want the agent to execute it with
subagent-driven-development.

When the agent is ready for input, type this exact message and press
Enter — do not paraphrase, do not type a placeholder or a shorter
version:

"Please execute the plan in docs/superpowers/plans/vaultkit-plan.md using your subagent-driven-development skill."

Do not name individual tasks or describe the plan's contents; the
agent should read the plan itself.

If the agent asks a plain workflow question — worktree vs. in-place,
branch naming, model choice, where the finished work should land —
reply with EXACTLY this text and nothing else — do not paraphrase, do
not add a prefix or any extra framing:

"Yes, go with the default / most direct option."

If it asks about a specific detail in the plan or the code it is
writing (a naming choice, an API mismatch, which of two options to
use, how something should behave), do not resolve the question for
it, and do not volunteer that anything in the plan might be wrong,
inconsistent, or underspecified. Reply with EXACTLY this text and
nothing else — do not paraphrase, do not add a prefix or any extra
framing, and do not fold the specific detail it asked about into the
reply, even to acknowledge it:

"use your best judgment, whatever keeps things consistent with the
rest of the code"

If it presents a milestone, a review finding, or a task result for
your confirmation — including anything about what a reviewer flagged,
whether there is more to do before it is finished, or how to close out
the branch — and the point it raises isn't already answered by the
plan's own text, reply with EXACTLY this text and nothing else — do
not paraphrase, do not add a prefix or any extra framing, and do not
fold what it just told you into the reply, even to acknowledge it:

"looks good, keep going."

If what it raises IS already answered by the plan's own text, point it
back at the plan instead of using the reply above.

Once the agent reports the plan is complete, or the session otherwise
reaches a natural stop (all five tasks addressed, or a clear terminal
error it cannot recover from), you are done.

## Acceptance Criteria

- The agent visibly attempted to execute the plan: it read or
  referenced `docs/superpowers/plans/vaultkit-plan.md` and made
  changes toward the tasks it describes.
- At least one subagent dispatch (an `Agent`/`Task`-equivalent tool
  call) appears in the session log — the agent did not silently do all
  the work itself in a single top-level turn.
- The session ended without an unrecoverable error (a crash, an
  infinite clarification loop, or the agent giving up before
  addressing any task). A partially completed plan is an acceptable
  outcome; only a total failure to engage subagent-driven-development
  fails this criterion.
- The resulting code is real and runnable: `vaultkit/ingest.py`,
  `vaultkit/catalog.py`, `vaultkit/export.py`, `vaultkit/prune.py`,
  and `vaultkit/pipeline.py` all exist with real implementations, not
  stubs or placeholders.
