Receber por email
← Voltar para o catálogo

ariff-claude-plugins

65 plugins that turn Claude Code into an autonomous development team. 24 agents, 34 skills, 5 hooks. Includes 12-plugin anti-hallucination suite. One-line install.

12estrelas
Atualizado há 7 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add a-ariff/ariff-claude-plugins

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/ariff-claude-plugins-mpt9k0ic/svg)](https://www.skillteca.com.br/skills/ariff-claude-plugins-mpt9k0ic)

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Executing Plans

Purpose

Execute plans in controlled batches with verification gates.

"I'm using the Executing Plans skill to implement this plan."

The Process

Load Plan → Review → Execute Batch → Report → Feedback → Next Batch

Step 1: Load & Review

  1. Read the plan file
  2. Review critically - identify concerns
  3. If concerns → Raise with user before starting
  4. Create TodoWrite for all tasks

Step 2: Execute Batch

Default batch size: 3 tasks

For each task:

  1. Mark as in_progress
  2. Follow each step exactly
  3. Run verifications as specified
  4. Mark as completed

Step 3: Report

After each batch:

## Batch Complete

**Implemented:**
- Task 1: [summary]
- Task 2: [summary]
- Task 3: [summary]

**Verification:**
\`\`\`
[test output]
\`\`\`

Ready for feedback.

Step 4: Continue

Based on feedback:

  • Apply changes if needed
  • Execute next batch
  • Repeat until complete

When to STOP

🛑 Stop immediately when:

  • Hit a blocker (missing dependency, unclear instruction)
  • Test fails unexpectedly
  • Plan has gaps preventing progress
  • You don't understand something

Ask for clarification. Don't guess.

Verification Rules

Before marking ANY task complete:

  1. Run the verification command
  2. Read the FULL output
  3. Confirm it matches expectations
  4. Only THEN mark complete

No "should work" or "looks good" - actual verification output.

Batch Reporting Format

### Batch N Complete

| Task | Status | Verification |
|------|--------|--------------|
| Task X | ✅ | 12/12 tests pass |
| Task Y | ✅ | Build successful |
| Task Z | ⚠️ | Needs review |

**Next batch:** Tasks A, B, C

Continue?

Completion

After all tasks:

  1. Run full test suite
  2. Verify all requirements met
  3. Report final status
  4. Hand off to finishing-branch skill if applicable
Compartilhar X LinkedIn