dev

Dev

Invocation: kc-dev-flow-2:dev

Package root: ${CLAUDE_PLUGIN_ROOT} <package> in this skill and its linked files is this root. If the value above is not an absolute path, the root is two directories above this SKILL.md.

Read the framework. This is a start/resume entry, not a worker stage or a second workflow controller. Claude's packaged command is /kc-dev-flow-2:dev; bare /dev is not a promised cross-host alias.

Resolve the absolute project root, explicit workflow directory and intended work item from the request and authoritative project/task records. Reuse established context; do not guess between projects or tasks. Read applicable project conventions and the existing context needed for the requested work.

After resolving the code root, run python3 <package>/scripts/learning.py --repo <absolute-code-root> notices --all. Present relevant unread learning results (items with unread true) to the user, distinguishing pending/uncertain, no-change, local proposal, PR and observed merge; pending proposals are not active rules. Only after actual presentation, run ack --job <job> --expected <notice_digest> for each shown snapshot. Context injection or reading alone is not presentation. A changed digest stays unread; interruption may repeat a notice. Settle every delivery shown open, acknowledged or not, by reading its PR with gh pr view as learn's Follow the delivery to a recorded end says, before presenting. Read failure holds that learning action, not unrelated approved development. This entry-level check is not a host SessionStart hook. Use learn for an explicitly requested named-task loop; notices do not authorize evaluation, delivery, retry or merge.

For existing work, preserve its recorded variant/profile, approved outcome, scope, non-goals and stop condition. Read current state, reports and delivery status instead of assuming a prior conversation is current. An invalid profile, conflicting records or missing authority holds the dependent action; return only the unresolved decision to the user. Do not restart approved design or ask again for an unchanged selection.

For new work without a profile selection, establish the intended outcome and recommend a profile using the framework's intended use and applicable shared profile principles. Ask the user to select it before profile-dependent work. An explicit valid selection is sufficient; FO records it with the variant in the work item through the existing workflow. Recommendation is not selection.

Hand the resolved project root, explicit workflow directory, work item, approved selection/scope and bounded outcome to spacedock:first-officer, with this skill's Package root: value, which FO writes into the scope notes of every worker dispatch and follow-up message with a line telling the worker to send its completion message to main, because the completion block Spacedock appends names team-lead. Retain that workflow directory as --workflow-dir on SD commands; cwd alone is not the binding. If FO is already active, continue there. SD owns stage selection, live worker availability, dispatch, reports, gates and recovery; a resumed FO does not establish that its old worker still exists. An entity sitting in a stage declared gate: true is excluded from spacedock status --next and from --boot's DISPATCHABLE table before the concurrency check runs (Spacedock v0.27.0, internal/status/format.go, dispatchAnalysis, reason gate), so an empty dispatchable view does not mean no worker is available; three of this workflow's five stages (backlog, ideation, validation) declare gate: true, so that empty view is this workflow's normal case, not the exception. Stage skills own profile routing and load the selected references in each worker's context.

Before each worker dispatch and on resume, run python3 <package>/scripts/workflow_checkout.py <workflow-dir>/README.md. Exit 1 means the README FO follows differs from the trunk's, exit 2 that it could not be compared; hold the dispatch, show the Captain the printed remedy or cause, and wait. Do not run the remedy or move the checkout yourself. This sentence sits here because a README old enough to be wrong may not contain it.