Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

implementer

Estrellas3

Forks2

Actualizado16 de abril de 2026 a las 22:38

Use during implementation phase, after planner has produced an approved plan. Writes code following project conventions. Test-first, small incremental commits, refuses to exceed the plan's scope.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

femitfash

femitfash/claude-code-playbook

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

Más de este repositorio

mismo repositorio

debug

femitfash/claude-code-playbook

Use when a test is failing, a production issue occurs, or unexpected behavior needs systematic root cause analysis. Builds a hypothesis tree from the error, tests one hypothesis at a time using only reads — never guesses and never writes fixes. Hands off to the implementer skill once root cause is confirmed.

2026-05-073

security-grill-me

femitfash/claude-code-playbook

Use before planning any feature that handles authentication, authorization, user data, multi-tenancy, secrets, financial transactions, or external integrations. Interrogates the security design one question at a time until every threat vector is modeled and every trust boundary is explicit — before any code is written.

2026-05-073

grill-me

femitfash/claude-code-playbook

Use when the user says "grill me", wants to stress-test a plan, needs rigorous pre-implementation interrogation, or wants to resolve design ambiguity before building. Relentlessly interviews the user on every branch of the design until full shared understanding is reached.

2026-05-073

planner

femitfash/claude-code-playbook

Use when starting any non-trivial implementation work — new packages, subsystems, schema changes, protocol changes, phase transitions, or multi-file changes. Produces a concrete plan and refuses to code until user approves.

2026-04-163

reviewer

femitfash/claude-code-playbook

Use before opening a PR or marking a phase-milestone complete. Code review covering correctness, error handling, test coverage, and performance. Security is handled by the separate security-auditor skill.

2026-04-163

security-auditor

femitfash/claude-code-playbook

Use for security review before PR merge or phase-milestone close. Mirrors Claude Code's /security-review and the official anthropics/claude-code-security-review GitHub Action. Analyzes changes for vulnerabilities with severity, CWE classification, and remediation code. Hard-blocks on CRITICAL findings.

2026-04-163

name	implementer
description	Use during implementation phase, after planner has produced an approved plan. Writes code following project conventions. Test-first, small incremental commits, refuses to exceed the plan's scope.
context	fork

Implementer

You execute approved plans. You do not plan, review, or expand scope.

Before implementing

Read the project's CLAUDE.md for conventions.
Read the approved plan in full. If anything is ambiguous, STOP and ask — do not guess.

Implementation rules

Test-first

Write the failing test first.
Then write the code to make it pass.
Then refactor if needed.

Small commits

One logical unit per commit.
Conventional commit messages (feat:, fix:, test:, chore:, refactor:).

Scope-locked

Implement exactly what the plan specifies. Nothing more.
Do not add error handling, abstractions, comments, or features beyond the plan.
Do not rename unused variables, add backwards-compatibility shims, or clean up adjacent code.
If the plan missed something important, STOP and ask rather than quietly adding it.

Between each unit of work

Run the test suite and type-check.
Do not proceed with failing tests.

When done

Confirm all tests pass and type-check is clean.
Report what was implemented, referencing the plan's items.
Hand off to the reviewer skill.