Stats
Actions
Tags
From minime
Blueprint a coding task from inline context or an existing blueprint. Reads the repo and org wiki page collections, scores and verifies them, thinks silently, self-challenges, and hands off to replicate. No human review gate. The blueprint is the durable handoff artifact.
How this skill is triggered — by the user, by Claude, or both
Slash command
/minime:blueprintWhen to use
When the user has a task to plan, whether as an existing blueprint file, inline conversation context, or a verbal description. This skill starts the orchestration flow.
This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Runs first in the four-phase flow. No human review gate. The output is an executable handoff for replicate.
Runs first in the four-phase flow. No human review gate. The output is an executable handoff for replicate.
Persist the living blueprint first.
Derive <org> and <repo> from git remote get-url origin. Use VIRTUCON_HQ from the session nudge, then env var, then ~/.minime.
Create or update VIRTUCON_HQ/<org>/_<repo>/blueprints/<YYYY-MM-DD>-<short-name>.blueprint.md.
Use VIRTUCON_HQ/templates/blueprint.template.md.
Read the file back from disk before proceeding.
Accept the task source from wherever it lives. Preserve the user's original request verbatim. If criteria are vague, nudge for EARS completeness with the minimum needed clarification. Every criterion must include an evidence method that names the proving tool, boundary, and pass/fail signal.
Locate wiki sources from the global layout. Read these paths when present:
VIRTUCON_HQ/schema.mdVIRTUCON_HQ/wiki/index.mdVIRTUCON_HQ/wiki/log.mdVIRTUCON_HQ/wiki/orgs/<org>/<repo>/VIRTUCON_HQ/wiki/patterns/VIRTUCON_HQ/raw/<org>/<repo>/
If the repo topic directory is empty, continue with zero repo wiki context and note that in the blueprint instead of blocking.
Legacy VIRTUCON_HQ/<org>/_<repo>/wiki/ and wiki.md files are compatibility input only. Prefer the global wiki tree whenever both exist.Discover domain-specific skills and agents. Scan local and installed skills or agents that might help the task.
Run VOI triage (see assets/ORCHESTRATION.md § VOI taxonomy for the full classification).
Resolve decided-by-data unknowns directly.
Dispatch only strong general-purpose subagents for needs-research items.
Research returns must lead with raw proof such as URLs, exact quotes, and code paths before interpretation.
Use ask_user only for undecidable-now tradeoffs.
Record every resolution in the Decisions table.
Rank wiki pages before reading them deeply.
Rank by Scope match, title or summary match, active status, stronger code citations, recency, and user-correction origin.
Read only the small set needed for the task.
Treat index.md and log.md as navigation aids first, not as final truth.
Verify before trusting. Open cited code paths from selected pages. If a page makes an uncited claim, mark it as a lead only. If a cited claim no longer matches live code, ignore it for planning and flag it for extract as stale.
Plan silently and persist the handoff.
Write a ## Plan summary with files to touch, implementation order, fix shape, tests, and resolved wiki constraints.
Critique the test strategy. Use a rubber-duck style review so each criterion is backed by a user-facing proof and at least one meaningful edge case.
Self-challenge briefly. State the riskiest assumption, when the approach would be wrong, and any remaining ambiguity.
Hand off.
End by instructing: now invoke skill("replicate") with the persisted blueprint path.
assets/ORCHESTRATION.md for the shared raw/wiki/schema contract.npx claudepluginhub abossard/virtucon --plugin minimeCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.