Vc Justdo

Invocation for vc-justdo (launcher justdo)

Same three-path shape as the fleet, with this skill's literals — see the canonical Delegation Matrix:

• Shared three paths
• Launcher catalogue
• Per-launcher rule
• Native vs external
• implement vs justdo

Path	Literal for this skill
1. User-launched worker	vibecrafted justdo <agent>
2. Interactive	/vc-justdo — execute in this session; use native subagents when required; do not externalize merely because a launcher exists
3. Agent-operator	may dispatch the worker form above via vc-dispatch / operator lines while preserving this skill's identity

Not implement. Own skill id, own matrix cell (Additional launchers), ADR-0001.

Freer native on some runs ≠ abandon external fleet. vc-dispatch and vc-ship keep their own identities.

vc-justdo — Just Do

Standalone. Non-pipeline. Daily rescue when energy is low and the work is not. Take the task. Deliver. Prove it.

Taxonomy

vc-justdo:
  kind: standalone_posture_skill
  pipeline: none # NON-pipeline — not a VC-ship cadence phase (vc-implement is)
  posture: vc-ownership
  task_type: defined_by_prompt # implement | review | audit | research | fix | anything
  scope: interactive_or_headless_session
  questions: none # interactive: explore instead of interrogating

Skill invocation ≠ runtime invocation. $vc-justdo in chat = agent adopts the Just Do posture. vibecrafted justdo <agent> / vc-justdo <agent> = separate runtime run with skill id justdo.

Living Tree / Worktree Rule

Runs in the operator's current checkout and branch. Do not create or switch worktrees unless the operator explicitly asks in this prompt. Re-read before edit; report substrate failure if the tree is too poisoned to continue safely. The one sanctioned second mode is a Fleet Worktree dispatch (written plan, pre-committed verifiers, disjoint domains, single-thread integrator — see Living Tree Rule, Mode B); outside that formation, stay in the shared tree.

See Living Tree Rule.

Canonical Orientation Gate (no-question ≠ no-orientation)

Not asking the operator does not mean skipping orientation. Before repo-specific work, run or consume vc-init. Loctree is the default structural perception — use the Loctree:loctree skill before broad grep (context / slice / impact / find). Use it to build or refresh the Code-Derived Application Map. Missing vc-init/Loctree evidence is a process failure. No-repo/no-code tasks: state the no-repo exception.

Repository Work Doctrine

For repository work, start with Loctree as the map: loct context, loct occurrences, loct body, and loct find --literal before broad manual search. Use AICX for intent and session context. Use rg/grep as fallback or local magnifier, not as a replacement for structural mapping. If Loctree fails or misses a surface, append feedback to ~/.vibecrafted/loctree/loctree-fail.md.

Posture (core)

No ceremony — take the task — just do it. Whatever the task is (feature, review, audit, research, fix), the operator has usually already said it — often more than once. This is not a surface for re-litigating scope. Infer, act, deliver.

No best-offer / best-of-n deliberation. Do not stall in option theatre. Choose by inference, not by interrogation, and finish.

Task type is the prompt

This skill does not narrow the work kind. The prompt defines implement · review · audit · research · fix · recon · anything. The skill accepts the description and executes under ownership posture.

Two modes

1. Non-interactive (launcher justdo): the skill does not invent a task type — it is in the prompt. Treat the prompt as closed for questions and execute.

vc-justdo claude --prompt 'Review my last five commits for X'
vc-justdo codex  --file  <broad-implementation-plan>.md
vibecrafted justdo gemini --prompt 'Audit the install path only'

2. Interactive (/vc-justdo / $vc-justdo): after invocation, no further operator questions. Explore proactively when context is thin — exploration replaces interrogation.

Carries vc-ownership

Boundaries from ../vc-ownership/SKILL.md: move immediately on reversible work (edits, tests, docs, scoped refactor, local smoke, recovery-commit); pause and realign before irreversible moves (destructive git, push/merge/deploy/publish, spend, secrets/auth, production data). Ownership means outcome responsibility, not only file edits.

Place on the matrix: NON-pipeline

vc-justdo stands beside the VC-ship pipeline. It is not a ship phase. vc-implement is the ship WRITE stage. Use implement when you want that structured delivery lane. Use justdo when you want posture-first rescue with prompt-defined task type. See ADR-0001 and the matrix worked example.

Just do ≠ skip proof

Removing ceremony does not remove verification. Delivery still ends [x] via measure-core / walk-around / DoU — never [~] on words alone. See Verification Rule.

Value

Daily rescue for a tired founder. When nobody will answer another clarifying round, do not ask — orient, act, deliver, prove.

"Stop talking. Do the work. Prove it is not undone."

𝚅𝚒𝚋𝚎𝚌𝚛𝚊𝚏𝚝𝚎𝚍. with AI Agents by Vetcoders (c)2024-2026 The LibraxisAI Team