CLI + Claude Code plugin that scaffolds and upgrades AI development harnesses — from vibe coding to autonomous spec-driven development
openbooklet.com/s/joycraftopenbooklet.com/s/[email protected]GET /api/v1/skills/joycraft> **Parent Brief:** `docs/briefs/2026-05-09-collaborative-mode-draft.md` > **Status:** Complete > **Date:** 2026-05-09 > **Estimated scope:** 1 session / 4 files / ~250 lines incl. tests > **Depends on:** `add-migration-module.md`, `update-doc-producing-skills.md`
> **Parent Brief:** `docs/briefs/2026-03-25-incremental-knowledge-capture.md` > **Status:** Ready > **Date:** 2026-03-25 > **Estimated scope:** 1 session / 3 files / ~120 lines
> **Parent Brief:** `docs/briefs/2026-03-23-joysmith-cli-plugin.md` > **Status:** Ready > **Date:** 2026-03-23 > **Estimated scope:** 1 session / 1-2 files / ~100 lines
> **Parent Brief:** `docs/briefs/2026-03-23-joysmith-cli-plugin.md` > **Status:** Ready > **Date:** 2026-03-23 > **Estimated scope:** 1-2 sessions / 2 files / ~200 lines
> **Date:** 2026-03-26 > **Project:** Joycraft > **Status:** Complete
You are setting up Joycraft for a team. Solo defaults stay solo; this skill adds the team-only ceremony â `docs/areas/` folders, area README/boundaries, and a thin team-facing CONTRIBUTING-joycraft doc.
> **Parent Brief:** `docs/briefs/2026-03-26-bugfix-workflow-skill.md` > **Status:** Complete > **Date:** 2026-03-26 > **Estimated scope:** 1 session / 1 file / ~150 lines
> **Parent Brief:** `docs/briefs/2026-03-30-crispy-harness-upgrades.md` > **Status:** Complete > **Date:** 2026-03-30 > **Estimated scope:** 1 session / 2 files / ~100 lines
> **Parent Brief:** `docs/briefs/2026-03-26-test-first-new-feature.md` > **Status:** Complete > **Date:** 2026-03-26 > **Estimated scope:** 1 session / 2-3 files / ~80 lines
> **Parent Brief:** `docs/briefs/2026-03-30-crispy-harness-upgrades.md` > **Status:** Complete > **Date:** 2026-03-30 > **Estimated scope:** 1 session / 2 files / ~120 lines
> **Parent Brief:** `docs/briefs/2026-03-26-test-first-new-feature.md` > **Status:** Ready > **Date:** 2026-03-26 > **Estimated scope:** 1 session / 2-3 files / ~100 lines
You have a Feature Brief (or the user has described a feature). Your job is to decompose it into atomic specs that can be executed independently â one spec per session.
You are producing a design discussion document for a feature. This sits between research and decomposition â it captures your understanding so the human can catch wrong assumptions before specs are written.
You have exactly one atomic spec file to execute. Your job is to implement it using strict TDD â tests first, confirm they fail, then implement until green.
You are guiding the user through setting up Level 5: the autonomous feedback loop where specs go in, validated software comes out. This is a one-time setup that installs workflows, creates a scenarios repo, and configures the autofix loop.
You are helping the user brainstorm and explore what they want to build. This is a lightweight, low-pressure conversation â not a formal spec process. Let them yap.
Capture a project fact and route it to the correct context document -- production map, dangerous assumptions, decision log, institutional knowledge, or troubleshooting
First-run onboarding pass that populates the project context layer -- read what context already exists, then offer a gap-only interview and batch-write the missing fact rows and long-form reference docs
Generate constrained execution boundaries for an implementation session -- NEVER rules and deny patterns to prevent agent overreach
Spawn an independent verifier subagent to check an implementation against its spec -- read-only, no code edits, structured pass/fail verdict
Auto-indexed from maksutovic/joycraft
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.