Skills

This index documents the live framework inventory in skills/ and the routes currently exposed by scripts/vibecrafted.

CI mode means the skill can run headless from the launcher without requiring a zellij-attached operator tab. Stand-alone means the operator has a direct command-deck entry instead of reaching the surface only through another mode or workflow.

Skill	Purpose	Primary entry	CI mode	Stand-alone	Docs
`vc-agents`	External execution fleet and agent-mode dispatch contract.	`vibecrafted <agent> implement\|research\|review\|plan\|prompt\|observe\|await`	Yes	No	SKILL · FLOW
`vc-decorate`	Late-stage visual finishing and coherence pass.	`vibecrafted decorate <agent>`	Yes	Yes	SKILL · FLOW
`vc-delegate`	Native in-session delegation for small bounded cuts.	`vibecrafted delegate <agent>`	Yes	Yes	SKILL · FLOW
`vc-dou`	Definition of Undone audit across repo, runtime, packaging, and market surface.	`vibecrafted dou <agent>`	Yes	Yes	SKILL · FLOW
`vc-followup`	Post-implementation direction audit for gaps, drift, regressions, and next leverage.	`vibecrafted followup <agent>`	Yes	Yes	SKILL · FLOW
`vc-hydrate`	Packaging, SEO, onboarding, and go-to-market hydration.	`vibecrafted hydrate <agent>`	Yes	Yes	SKILL · FLOW
`vc-implement`	Autonomous end-to-end implementation with followup and marbles built in.	`vibecrafted implement <agent>`	Yes	Yes	SKILL · FLOW
`vc-init`	Context bootstrap: history, structure, gates, and operator-session handoff.	`vibecrafted init <agent>`	No	Yes	SKILL · FLOW
`vc-intents`	Intention-to-runtime truth audit across plans, sessions, and code.	`vibecrafted intents <agent>`	Yes	Yes	SKILL · FLOW
`vc-marbles`	Truth-convergence loop for fixing what is still wrong.	`vibecrafted marbles <agent>`	Yes	Yes	SKILL · FLOW
`vc-ownership`	Full-spectrum operational ownership across code, runtime, docs, packaging, and ship surface.	`vibecrafted ownership <agent>`	Yes	Yes	SKILL · FLOW
`vc-partner`	Shared executive reasoning and collaborative planning with the user in the loop.	`vibecrafted partner <agent>`	Yes	Yes	SKILL · FLOW
`vc-prune`	Runtime-cone cleanup and dead-surface removal.	`vibecrafted prune <agent>`	Yes	Yes	SKILL · FLOW
`vc-release`	Release prep, deployment truth, and outward ship checks.	`vibecrafted release <agent>`	Yes	Yes	SKILL · FLOW
`vc-research`	Triple-agent research swarm.	`vibecrafted research --prompt\|--file`	Yes	Yes	SKILL · FLOW
`vc-review`	Findings-first review over a bounded PR, branch, commit range, or artifact pack.	`vibecrafted review <agent>`	Yes	Yes	SKILL · FLOW
`vc-scaffold`	Founder-first architecture planning from vague intent.	`vibecrafted scaffold <agent>`	Yes	Yes	SKILL · FLOW
`vc-workflow`	Examine -> Research -> Implement pipeline.	`vibecrafted workflow <agent>`	Yes	Yes	SKILL · FLOW

Route notes

Artifact root: $VIBECRAFTED_HOME/artifacts/<org>/<repo>/<YYYY_MMDD>/
Lock path: $VIBECRAFTED_HOME/locks/<org>/<repo>/<run_id>.lock
Generic spawned skills write reports/<timestamp>_<slug>_<agent>.md with matching .transcript.log and .meta.json sidecars under the date root.
vc-marbles uses the same root but nests loop artifacts under marbles/.
vc-init is interactive-only and prepares the operator session; it does not guarantee a report on its own.
vc-implement / vibecrafted implement is the official autonomous delivery face. vc-justdo, vibecrafted justdo, and per-agent *-justdo helpers are compatibility aliases only; they stay listed here so installed operator environments do not silently break.
Every vc-* workflow skill inherits the Living Tree rule: stay in the operator’s current checkout and branch; do not create or move into git worktrees unless the operator explicitly asks for a worktree in that prompt.
vc-review needs a bounded review target: a PR number, branch diff, commit range, or generated review artifact pack.
vc-followup is intentionally broader: it audits the post-implementation direction across code, runtime, UX, docs, packaging, and next leverage.
vc-partner keeps the user and agent in shared steering. vc-ownership means the agent takes operational ownership; neither mode implies delegation unless the operator explicitly invokes a delegation surface.

Compatibility aliases

Alias	Canonical command	Why it remains
`vc-justdo`	`vc-implement`	Existing agents and shell environments know it.
`justdo`	`vibecrafted implement`	Internal run IDs and compatibility still use `just`.

The framework-level chaining map lives in WORKFLOWS.