claude

craft

Universal coding workflow plugin: a 9-phase loop with explicit knowledge management, autonomy controls, vertical slicing, and bug-verification — works identically across shell scripts, libraries, REST APIs, full-stack apps, and infrastructure code.

0 on GitHubby Christoph Raschkev2.2.0MITupdated yesterdaydevelopment
/

Plugin craft from marketplace craft in ChriRas/craft. Commands read from the repo's manifest — today.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (16)

  • docs-site

    Regenerate or update the bilingual GitHub Pages documentation site (docs/index.html) after the plugin changes. Defines the design contract, the section/anchor structure, the four-perspective analysis procedure, delta-vs-full update, and the verification gate. Trigger phrases; "update the docs site",

  • brainstorm

    Facilitate structured, collaborative brainstorming sessions using proven ideation techniques (SCAMPER, Five Whys, First Principles, etc.). Slash-invocable as `/craft:brainstorm [topic]`. Phase 1 entry point of the CRAFT workflow.

  • craft

    State-aware entry point for the CRAFT workflow. When invoked as /craft, detect whether the current project is onboarded, whether any slices are in progress, and offer the user the actions valid for that state. Does not execute sub-actions itself — only orients and recommends.

  • debug

    Bug verification protocol — four-step ALIGN → PROTOCOL → AUTONOMOUS LOOP → ESCALATION flow. Use this skill when the user types `/craft:debug`, when the user explicitly says "I have a bug", "let me debug X", "this is broken", or when the agent detects it has made 2 or more fix attempts on the same sy

  • grill-me

    Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree one question at a time. Slash-invocable as `/craft:grill-me [plan-or-subject]`. Phase 2 entry point of the CRAFT workflow; also usable anytime outside Phase 2 to str

  • senior-developer

    The CRAFT Senior-Developer baseline — universal engineering stance, quality hierarchy, workflow gates, test-discipline matrix, and problem-playbook. Loaded by /craft:prime and active in every phase. Stack-agnostic; framework idioms live in stack-packs.

  • stack-bash

    CRAFT stack-pack for shell projects written in Bash — scripts, tooling and libraries on bash 5 (quoting, arrays, set -euo pipefail and its pitfalls, traps and temp files), script and library structure, portability to POSIX sh and macOS's /bin/bash 3.2, ShellCheck and shfmt, and bats-core test patter

  • stack-php-api-platform

    CRAFT stack-pack for API Platform on Symfony — the current line (5.0) with the 4.4 differences marked: resources (entity or DTO), state providers and processors, operations, validation and security, filters and pagination, formats (JSON-LD/Hydra, OpenAPI, JSON:API, HAL, JSON Merge Patch), GraphQL, M

  • stack-php-laravel

    CRAFT stack-pack for PHP + Laravel projects — language idioms, framework patterns, and Pest test patterns. Loaded by /craft:build, /craft:test, and /craft:refactor when a project declares it. Not auto-activated.

  • stack-php-shopware5

    CRAFT stack-pack for maintaining legacy Shopware 5 shops and plugins (end-of-life since July 2024, last release 5.7.20) — safe change without upstream patches, the 5.2+ plugin system and the legacy Bootstrap.php system, Smarty templates and themes, the ExtJS backend and the REST API, pragmatic PHPUn

  • stack-php-shopware6

    CRAFT stack-pack for Shopware 6 extensions on the 6.7 line with the older 6.6 line's differences marked — plugins (services, subscribers, migrations, scheduled tasks, routes), the Data Abstraction Layer, apps (manifest, webhooks, app server, app scripts), the Storefront and themes, the Administratio

  • stack-php-symfony

    CRAFT stack-pack for Symfony applications on the current line (8.x) with the 7.4 LTS differences marked — dependency injection and configuration, controllers and routing, Doctrine ORM, Messenger, Security, Twig and Forms, and PHPUnit tests with KernelTestCase and WebTestCase. Loaded by /craft:build,

  • stack-php

    CRAFT stack-pack for plain PHP projects without a framework (libraries, CLI tools, small apps) — language idioms, Composer project patterns, and PHPUnit test patterns with PHPStan and PER Coding Style as the quality rules. Loaded by /craft:build, /craft:test, /craft:refactor and /craft:review when a

  • stack-python

    CRAFT stack-pack for plain Python projects without a web framework (libraries, CLIs, scripts, services) — language idioms, typing and async basics, a uv + Ruff project setup around pyproject.toml, and pytest test patterns with mypy as the type checker. Loaded by /craft:build, /craft:test, /craft:ref

  • stack-ts

    CRAFT stack-pack for plain TypeScript projects on Node without a frontend framework (libraries, CLIs, services) — strict typing, narrowing, error handling and async idioms, an ESM-only npm project setup (tsconfig, package.json exports, build), ESLint + Prettier, and Vitest test patterns. Loaded by /

  • workflow

    The 9-phase coding loop — the methodological backbone of this plugin. Loaded by every phase command. Defines phase semantics, transition rules, knowledge model, autonomy taxonomy, and the rule-conflict policy. Use whenever a slash command needs to know "what phase am I in and what is allowed here?".

Slash commands (24)

  • /craft:abort

    Abandon a slice. Asks confirmation, then closes the plan file by default — deleted, or moved into .claude/plans/.closed/ when the user's settings deny or ask on removing it. Aborted slices have no archive value — they leave only their (possibly partial) commits behind, which the user manages separat

  • /craft:block

    Record a first-class `blocked` state on the active slice when work cannot proceed until a prerequisite — itself a unit of work or a decision — is resolved. Classifies the blocker, writes on-demand frontmatter + a ## Blocker section, and routes prerequisite work to its own slice/epic without spawning

  • /craft:build

    Phase 4 — implement the active slice. Loads project-local specialist skills lazily, works sub-tasks in order, runs tests silently, bundles at sub-task boundaries.

  • /craft:checkout

    Switch into a slice- or epic-worktree for human inspection during Recap / Review. Read-only — resolves the worktree path, prints the cd instruction and the stack-pack provisioning hint. Does not install anything.

  • /craft:commit

    Phase 9 — atomic commits, decisions promotion dialog, slice archive write, plan file closing (deleted, or moved into .claude/plans/.closed/ under a rule on removing files). On a pull-request + Protected-main profile it opens a PR and merges via gh only after a GitHub approval ("Freigabe ≠ Merge"). T

  • /craft:continue

    Resume work on an active slice. Routes automatically to the right phase command based on the slice's recorded Status. Use after /craft:prime when picking up where you left off.

  • /craft:epic

    Plan a multi-slice epic — captures Vision and initial Slice Decomposition, writes an epic plan file under .claude/plans/.

  • /craft:execute

    Autonomously execute an epic or single slice. Parallel worktree mode (default) creates parallel git worktrees and delegates Phase 4–7 to subagents per slice, merging into an epic-branch; in-place mode builds a single slice on a branch in the main checkout, halts before Phase 5 for IDE review (resume

  • /craft:handoff

    Fresh-context restart. Summarizes problem + attempts into the slice plan's ## Handoff section so a new chat session can pick up cleanly. Useful when context is poisoned or progress stalls.

  • /craft:intent-update

    Propose an explicit edit to .claude/project/intent.md. Agent drafts the diff, human confirms before write. Used outside Phase 9 when an intent shift surfaces.

  • /craft:onboard

    One-time project onboarding — bootstraps `.claude/project/` for fresh projects or migrates an existing `.claude/` setup. Detects existing content automatically and switches to migration sub-path.

  • /craft:pause

    Pause the active slice mid-phase. Records the pause note in the slice plan; slice stays open and resumable. Use when stepping away or context-switching.

  • /craft:plan

    Phase 3 — plan a new vertical slice. Dialogically forces the three universal questions (trigger / observable effect / test strategy) and writes a slice plan file.

  • /craft:prime

    Session-start context loader. Checks tools, loads project knowledge, validates Rules ↔ State, lists active slices, and recommends the next action. Auto-runs on SessionStart when the project is onboarded.

  • /craft:recap

    Phase 6 — explain what was built and why. Captures the slice's What / Why / Decisions; offers a Mermaid diagram for complex slices. Draft becomes the slice archive entry in Phase 9.

  • /craft:refactor

    Phase 7 — small structural improvements before Review (Phase 8). Asks the three Thorstensen prompts dialogically. Max 2–3 refactor items per slice; larger refactor = its own slice.

  • /craft:release

    Release an in-place slice halted for IDE review — the explicit "I've reviewed the raw diff, proceed" gesture that resumes the slice past the pre-Phase-5 halt toward the commit. Only for slices at Status awaiting-release (set by /craft:execute in in-place mode).

  • /craft:review

    Phase 8 — independent fresh-eyes code review of the slice. A subagent with a clean context window classifies findings on the severity × fix-nature rubric; bounded local edits are fixed in-phase, the rest escalate, and Commit is gated until heavy needs-rethinking findings are resolved.

  • /craft:status

    Lightweight slice overview. Reports active slices, phases, and sub-task progress without re-loading project context. Read-only, never modifies anything.

  • /craft:test

    Phase 5 — hands-on user verification. Prepares a demo (5a), the user exercises the artifact (5b), structured feedback is captured (5c). Bugs trigger /craft:debug; UX issues iterate.

  • /craft:unblock

    Clear a `blocked` slice. Presents the resume | re-plan | abort fork and restores the slice to the exact execution status it was blocked at; also back-fills a `(pending)` prerequisite marker with the real slice/epic-ID once it exists. The mutating counterpart to /craft:block; /craft:continue routes h

  • /craft:upgrade

    Update the CRAFT plugin marketplace clone from GitHub. Syncs the marketplace, shows incoming commits, requires explicit confirmation, then names how Claude Code installs the new version (auto-update or `/plugin update`) and that a new session loads it. Pre/Post-Assertions, no silent mutations.

  • /craft:worktree-clean

    Detect orphaned CRAFT worktrees (whose plan is archived or missing) and remove them after user confirmation. Durable-state mutation.

  • /craft:worktree-status

    List every active CRAFT-managed git worktree with slice/epic-ID, branch, path, last activity, and handoff-marker presence. Read-only.

Subagents (4)

  • code-reviewer

    Fresh-context code reviewer for CRAFT Phase 8. Receives the review brief assembled by `/craft:review` (Senior-Developer baseline, optional stack-pack, slice plan, prior slice archives, the diff under review, the Phase-6 recap, earlier review rounds on a re-review, the findings rubric) and returns a

  • plan-architect

    Fresh-context architecture review of an epic's open slice plans during a `/craft:execute <epic-NNN> --autopilot` run, before the plan gate. Reads every open plan of the epic (pipeline and hand-planned), the epic's Vision and design record and the landed slices' archives, verifies earlier plan-review

  • slice-builder

    Autonomous Phase 4–7 executor for one slice during a `/craft:execute` run. Runs inside a slice-worktree (in an autopilot run, in the main checkout on the epic branch), delegates to `/craft:build → /craft:test → /craft:recap → /craft:refactor → /craft:review` in subagent mode, writes `.craft/handoff.

  • slice-planner

    Phase 3 planner for one epic entry during a `/craft:execute <epic-NNN> --autopilot` run. Receives the epic plan, the entry, a slice-ID and plan path the master already allocated (and, on an `[R]` round, the human's revision note), answers the three universal questions from the epic's Vision, its des

Hooks (5)

  • SessionStart

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh"

  • SessionStart

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/worktree-handoff-notify.sh"

  • UserPromptSubmit

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/cache-guard.sh"

  • UserPromptSubmit

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/pause-watch.sh"

  • PreToolUse

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/readonly-context-guard.sh"

View source on GitHub chriras.github.io

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

mem0

claudecodex

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

mem0ai/mem0 68,893

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.

5 commands

HKUDS/CLI-Anything 58,665

Automates browser interactions for web testing, form filling, screenshots, and data extraction

12 skills

vercel-labs/agent-browser 50,373

Use Alibaba Open Code Review from local Codex.

2 skills

alibaba/open-code-review 50,068

Maintain craft?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted