engineer

Dispatch the Engineering Team to implement something. Takes a task description (or a research SYNTHESIS reference) and runs the full plan-then-build protocol with verifier + reviewer loop. Use this skill IMMEDIATELY when the user asks to implement, build, fix, refactor, add a feature, ship code, or apply a research finding. Examples: "implement Hook A from memory research", "fix the auth bug", "refactor the routing module", "add dark mode", "apply the changes from the research session".

Ir para a instalação

Repositório: TheAdaply/re-forge
Última atividade na origem: 4 de junho de 2026 às 07:05
Idioma detectado do SKILL.md: inglês
Estrelas: 0
Forks: 0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/TheAdaply/re-forge --skill engineer

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

causal-inference

Correlation-to-causation discipline for any "does X cause Y", "what is the effect of X", or "should we do X" question. Use when a decision rests on a causal claim drawn from observational data, an A/B test, an event study, or a regression with controls — before reporting any effect as causal. Enforces draw-the-DAG-first, identification-before-estimation, the design hierarchy (RCT > natural experiment > diff-in-diff > IV > controls), A/B-test pitfalls, and unmeasured-confounder sensitivity analysis.

2026-06-11

nnsight

Provides guidance for interpreting and manipulating neural network internals using nnsight with optional NDIF remote execution. Use when needing to run interpretability experiments on massive models (70B+) without local GPU resources, or when working with any PyTorch architecture.

2026-06-11

spec-driven

Use this skill for long-horizon agentic coding where a feature spans many turns and the agent drifts: it freezes a re-readable contract before code. Writes EARS-style requirements -> design -> task breakdown -> verification evidence, one feature directory per feature, with status gates and grep-able traceability IDs. Triggers on 'spec this out', 'write a spec', 'spec-driven', 'requirements then design', or planning a multi-session build.

2026-06-04

Ver todas deste repositório

Engineering Team dispatch

You are invoking the Engineering Team (v1 protocol, 12 specialists).

What to do

Read ~/.claude/agent-memory/engineering-lead/MEMORY.md — lessons from past engineering sessions.

Read ~/.claude/agents/engineering/engineering-lead.md — adopt this as your behavioral contract.

If the user references a research session, read its SYNTHESIS.md at <cwd>/.claude/teams/research/<slug>/SYNTHESIS.md as binding input.

Create the session workspace at <cwd>/.claude/teams/engineering/<slug>/.

Classify the tier:

Trivial (typo, rename, comment): executor + verifier only
Scoped (single-file logic, small feature): planner + executor + verifier + reviewer
Complex (multi-file, cross-module, cites research): full roster, all gates

Execute the protocol:

Phase A: CHARTER.md + planner + architect + plan-skeptic + plan-adversary (if external inputs)
Phase B: For each task — executor + verifier + reviewer (inner loop with debugger on failure)
Close: Evaluator (5-dim rubric) + retrospector + scribe

If cross-team, write handback to research workspace at close.

Hard rules

All Opus, all max effort

Tier up, never down — when uncertain, pick the higher tier

Verifier runs fresh tests (never trust executor's claim that "it works")

Reviewer is read-only (disallowedTools: Write, Edit)

3-failure circuit breaker on debugger → escalate to architect

DIFF_LOG.md and VERIFY_LOG.md are append-only

name

engineer

description

Engineering Team dispatch

You are invoking the Engineering Team (v1 protocol, 12 specialists).

What to do

Read ~/.claude/agent-memory/engineering-lead/MEMORY.md — lessons from past engineering sessions.
Read ~/.claude/agents/engineering/engineering-lead.md — adopt this as your behavioral contract.
If the user references a research session, read its SYNTHESIS.md at <cwd>/.claude/teams/research/<slug>/SYNTHESIS.md as binding input.
Create the session workspace at <cwd>/.claude/teams/engineering/<slug>/.
Classify the tier:
- Trivial (typo, rename, comment): executor + verifier only
- Scoped (single-file logic, small feature): planner + executor + verifier + reviewer
- Complex (multi-file, cross-module, cites research): full roster, all gates
Execute the protocol:
- Phase A: CHARTER.md + planner + architect + plan-skeptic + plan-adversary (if external inputs)
- Phase B: For each task — executor + verifier + reviewer (inner loop with debugger on failure)
- Close: Evaluator (5-dim rubric) + retrospector + scribe
If cross-team, write handback to research workspace at close.

Hard rules

All Opus, all max effort
Tier up, never down — when uncertain, pick the higher tier
Verifier runs fresh tests (never trust executor's claim that "it works")
Reviewer is read-only (disallowedTools: Write, Edit)
3-failure circuit breaker on debugger → escalate to architect
DIFF_LOG.md and VERIFY_LOG.md are append-only

engineer

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

Engineering Team dispatch

What to do

Hard rules

Engineering Team dispatch

What to do

Hard rules