mtk-agent-toolkit: Skill for Claude Code

MTK Implement — Full Feature Loop

MTK File Resolution

Resolve MTK skill/reference/script paths per .claude/references/mtk-file-resolution.md unless the router already stated MTK_ROOT=<path> this session; CLAUDE.md, .claude/tech-stack, .claude/rules/, tasks/, docs/, .mtk/ stay project-relative.

The entry point for substantial work. Stack specifics come from the active tech stack skill; the workflow detail lives in the skills each phase names (context-engineering, workflow-artifacts, brainstorming, spec-driven-development, planning-and-task-breakdown, incremental-implementation / subagent-implementation, security-and-hardening, spec-drift-detection, verification-before-completion, code-simplification) and in the implement-* references.

Phase 0: Load Context (Progressive Disclosure)

Before doing anything else:

1. Init or resume a workflow artifact (.claude/skills/workflow-artifacts/SKILL.md).
   • Resolve the helper once — plugin installs have no project-relative copy, and CLAUDE_PLUGIN_ROOT is never set in the Bash environment (Claude Code substitutes the braced ${CLAUDE_PLUGIN_ROOT} into skill text at load time instead), so a bare scripts/workflow-artifact.sh fails. Resolve it MTK_HELPER_ROOT-first (a checkout you pin — see CLAUDE.md), then project, then plugin, and use "$WFA" for every workflow-artifact.sh call in this skill:

     WFA="$([ -n "${MTK_HELPER_ROOT:-}" ] && echo "$MTK_HELPER_ROOT/scripts/workflow-artifact.sh" || ([ -f scripts/workflow-artifact.sh ] && echo scripts/workflow-artifact.sh || echo "${CLAUDE_PLUGIN_ROOT}/scripts/workflow-artifact.sh"))"
     

   • Run "$WFA" list.
   • If a single active BUILD workflow exists for this feature, ask via AskUserQuestion whether to resume that uuid or start a new one.
   • Otherwise prune expired workflows, init, and emit the phase-0 marker in one call — the phase goes in --data, not as a positional: "$WFA" prune --older-than 30 >/dev/null; MTK_WF_UUID=$("$WFA" init BUILD --goal "<one-line user goal>") && "$WFA" event "$MTK_WF_UUID" phase_started --data '{"phase":"phase-0"}'. Remember the uuid for the rest of the session.
   • Bookkeeping rides along, never alone. Every later "$WFA" write in this skill is appended with && to the command it records (the lint, the checkpoint, the sidecar write) or grouped into one "$WFA" batch "$MTK_WF_UUID" <op> -- <op> … call. A standalone artifact write is a full model turn spent on one line of JSON. Only init, list, read, and verify-seal run alone.
2. Follow .claude/skills/context-engineering/SKILL.md: it resolves the stack for the files in scope (pass a representative change_manifest path when the change targets a subtree), loads the tech-stack-{stack} skill, and loads references per phase and per applyTo match. If neither AGENTS.md nor CLAUDE.md exists, stop and tell the engineer to run /mtk-setup. Phase 0 itself loads only the stack's coding guidelines and architecture-principles.md if present.
3. Query lessons for the initial scope (learnings.sh query --phase implement, else tasks/lessons.md, resolved from the main worktree).
4. Output intensity: --terse reports only decisions, actions, findings and evidence; --verbose adds rationale, alternatives and references consulted; default is brief rationale for non-obvious decisions.
5. Worktree pre-flight (capture only). Run git status --porcelain and remember the set of already-modified and untracked paths — the pre-existing dirty set. This is a read-only snapshot, not a gate yet. It feeds two later checks: (a) the spec's dirty-worktree risk step (spec-driven-development step 3b, for out-of-manifest paths), and (b) the Phase 2.9 worktree collision gate (for in-manifest paths — the parallel-session case). Capturing it now, before any edit, is what lets the collision gate tell "already dirty when we started" apart from "dirty because this workflow touched it."