convez.ai
SkillProdutividadeAvançado
jameskyeong

MekaKnight — Orquestrador de Produtividade para Claude Code

jameskyeong/mekaknight

Um comando `/forge` que orquestra o fluxo de desenvolvimento inteiro automaticamente

Ver no GitHub
InicialPluginScore · de 0 a 100

Skill que implementa `/forge`, um orquestrador unificado de desenvolvimento que executa pipelines completas (diagnóstico, prototipagem, refatoração) em um único comando, com roteamento automático por intenção. Deposita artefatos duráveis (planos, testes de regressão, ADRs, glossários) que aceleram sessões futuras através de engenharia composta.

Instalação

$npx convez-ai jameskyeong/mekaknight

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 3 dias
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Executar diagnóstico estruturado de bugs com reprodução via teste antes da correção
  • Prototipagem rápida com fases relaxadas para exploração, sem enforçar TDD rigidamente
  • Acumular decisões arquiteturais (ADRs), planos retomáveis e referências de disciplina no repositório
  • Redirecionar fluxo de trabalho com base em intenção declarada, sem escolher manualmente qual sub-skill invocar

Veredito

Skill técnico bem arquitetado para desenvolvedores que valorizam pipelines estruturados e compounding de artefatos. O `/forge` elimina fricção de orquestração manual e força verificação rigorosa em limites de fase — ideal para equipes que querem elevar padrão de entrega sem abandonar flexibilidade.

README

A tradução para o português deste README ainda está na fila.


Built on two pillars: /forge — a self-contained development orchestrator that drives the full flow from one command — and compound engineering baked into the structure, so every session deposits artifacts that lift the next one.

The rest (issue tracking, inspection) are opt-in utilities — supplementary, not required.

How /forge is different from other skill packs

Most skill packs (superpowers, Matt Pocock, etc.) hand you a toolbox of discrete disciplines and ask you to remember which one to invoke when. Each invocation starts fresh. /forge inverts both halves:

Pillar 1 — One command, smart pipeline

  1. One command, full pipeline. You type /forge (or /forge fix the login bug). Forge runs the whole flow — you never pick which sub-skill to call next.
  2. Auto-routing by intent. After Clarify, forge infers what kind of work this is and picks one of 4 routes. You don't choose; it decides.
  3. Different phase shapes per route. DIAGNOSE writes the reproduction test before the fix. PROTOTYPE relaxes TDD on purpose. These aren't relabeled flows — they're different phase orders.
  4. No-soft-language verification. Every phase boundary rejects "should work", "seems fine", "looks good". Verification means running the command and observing the output.
  5. Tracker-free core. Forge itself never reads or writes Notion. Issue tracking is a separate, opt-in surface.
  6. Self-contained. Zero dependency on superpowers, Matt Pocock, or any other skill pack — every discipline lives inside skills/forge/references/. See ADR 0001.

Pillar 2 — Compound engineering, in one skill

Each /forge session deposits durable artifacts in your repo so future sessions start ahead. Five channels, all automated — bundled into one orchestrator, no skill composition required. Discipline runs as part of the same flow that builds the code:

ChannelHow forge depositsWhat compounds
Plan filesAuto — PLAN route writes docs/plans/<feature>.mdResumable contracts. /forge docs/plans/<feature>.md re-enters from the first incomplete task across sessions.
Regression testsAuto — DIAGNOSE route adds the minimized reproduction test to the suite permanentlyBugs compound into protection. The net grows with every fix.
ADRsAuto-prompted — Retrospective phase proposes an ADR when an architectural choice was madeDecision history accumulates in docs/adr/. Future sessions know why.
Discipline referencesAuto-prompted — Retrospective proposes a references/<phase>.md append when a new failure mode surfacesIn-repo, editable discipline that grows with the project. Not vendor-locked.
Domain glossaryAuto-prompted — Retrospective proposes a CONTEXT.md entry when new terminology was introducedLanguage stays consistent across sessions and contributors.

The Retrospective phase runs between Verify and Finish, checks each channel against a threshold, and proposes deposits one at a time. Silent exit when no channel qualifies — performative deposits are explicitly rejected. See ADR 0007.

Your repo gets easier to work in over time. That's the compound part.

/forge — Development Orchestrator

The 4-way router

After Clarify, forge picks one route based on the kind of work. Each route is a meaningfully different phase shape — not the same flow renamed.

RouteWhenPhase shapeWhy it's different
DIRECTSmall contained change. 1-4 commits, tightly-grouped files.Build → Peer-review → Verify → FinishSkips plan file. No ceremony for a one-shot change.
PLANMedium feature. 5-15 commits, 2-4 files with shared state.Plan file → user confirms → sequential BuildPlan file becomes the contract; cross-session pickup runs off it.
DIAGNOSEBug-first work. Reproduction steps, error messages, "it's broken".Reproduce → Minimize → Investigate → Fix → Regression-preventThe reproduction test is written first and stays in the suite as the regression net.
PROTOTYPEThrowaway exploration. "How should this look", "try a few approaches".Time-boxed variations (relaxed TDD) → user reviews → Discard or PromoteTDD is intentionally relaxed. Promote = restart as a fresh PLAN run, not a graduation.

Flexible entry & resume

  • Resume mid-flow — /forge docs/plans/<feature>.md re-enters the plan, skips Clarify+Route, picks up from the first incomplete task.
  • Skip Clarify — say "skip clarify" or "requirements are clear" when you've already specced the work.
  • Called from /strike — the Notion issue title + body seeds Clarify automatically.

Phases at a glance

preflight → clarify → route → build (strict TDD) → peer-review → ship-check (slot) → verify → retrospective → finish
  • Relentless clarification — the 5-category ambiguity checklist must reach 0 items before Route.
  • Strict TDD — RED → GREEN → REFACTOR for every unit. No skipped tests, no commented-out tests, no "TODO: add test later".
  • Independent peer-review subagent — fresh perspective on the diff, free from author recency bias.
  • Retrospective — proposes ADR / references / CONTEXT.md deposits when the session produced learnings worth keeping. Silent exit otherwise.
  • Branch finish is explicit — local merge / open PR / keep branch / discard. Not an afterthought.

Decision history: ADR 0001 (self-contained), ADR 0005 (depth via references), ADR 0006 (DIAGNOSE + PROTOTYPE), ADR 0007 (Retrospective).


Supplementary skills

🔬 Inspection (alpha)

Ships in v2.0 but not the v2.0 headline — the author doesn't use them daily and dogfooding didn't surface real findings. Available if you want them; future direction tied to post-launch feedback. See ADR 0004.

CommandWhat it does
/lockv0.1 inspection for Supabase RLS gaps, secret-key client exposure (Next.js "use client" paradigm), missing Stripe webhook signatures
/launchv0.1 security GO / NO-GO deploy verdict from lock's findings (security-only by design — multi-axis aggregation is not promised, see ADR 0010)

Framework note: lock's secret-key check assumes a Next.js-style client/server boundary. SvelteKit / Nuxt / Remix may receive false PASSes on that specific check — manual review recommended for those stacks until framework-specific detection lands.

🗂 Notion issue tracking (optional integration)

Notion-backed issue lifecycle. From a Slack-pasted blob of bug reports to grouped, codebase-verified tickets — and back out into shippable fixes.

CommandWhat it does
/linkOne-time Notion connection — API key, database, property mapping, defaults
/tagParse a prompt into issues, auto-group related items, verify against the codebase, create pages
/strikePick a pending issue, call /forge to implement, update status with a human-readable outcome note

Why it's different — issue titles are written as user-visible problems, not git commit messages. Cross-functional readers (PMs, support, customers) can scan the tracker without engineering context.

Installation

claude plugins marketplace add https://github.com/jameskyeong/mekaknight.git
claude plugins install mekaknight

Requirements

License

MIT

Ver o original no GitHub

Bom para

Relacionados