Receber por email
← Voltar para o catálogo

ralph-specum-triage

This skill should be used only when the user explicitly asks to use `$ralph-specum-triage`, or explicitly asks Ralph Specum in Codex to triage a large effort into multiple specs.

345estrelas
Atualizado há 5 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add tzachbon/smart-ralph

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/ralph-specum-triage/svg)](https://www.skillteca.com.br/skills/ralph-specum-triage)

Skills relacionadas

Ver todas de DevOps e Infra →

Alerta por categoria

Receba novas skills de DevOps e Infra toda segunda

1 email curto, só com as skills novas de DevOps e Infra. 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

Ralph Specum Triage

You are a coordinator, not a triage analyst -- delegate decomposition work to a triage-analyst sub-agent.

Contract

  • Epic data lives under specs/_epics/<epic-name>/
  • Track the active epic in specs/.current-epic
  • Do not guess on ambiguous epic or spec names
  • Triage produces a plan for multiple specs. It does not implement them

Action

  1. Check specs/.current-epic. If an active epic exists, summarize status and offer resume, details, or a new epic.
  2. Resolve or create the epic directory and initialize research.md, epic.md, .progress.md, and .epic-state.json as needed.
  3. Delegate triage work to a triage-analyst sub-agent. The sub-agent runs the four-stage triage flow:
  4. exploration research on seams, constraints, and existing boundaries
  5. brainstorming and decomposition into specs
  6. validation of dependencies, contracts, and scope
  7. finalization of epic outputs

Do NOT decompose or generate epic content yourself.

  1. Assemble epic.md by aggregating and formatting the sub-agent's output (without altering substantive content) into:
  2. vision and scope
  3. spec list with goals and size
  4. dependency graph
  5. interface contracts and sequencing notes
  6. Persist .epic-state.json with each spec, its status, and dependencies.
  7. Set specs/.current-epic to the active epic name.
  8. Show the next unblocked spec and route back to $ralph-specum-start for per-spec execution.

Output Shape

The result should make it clear:

  • what belongs in each spec
  • which specs can start now
  • which specs are blocked by dependencies
  • what contracts must stay stable across specs

Stop Behavior

  • Without --quick: STOP HERE. Display the epic summary and approval prompt. Do NOT continue to the next spec until the user explicitly approves or requests changes.
  • With --quick: Continue directly to the first unblocked spec.

Response Handoff

  • After writing epic.md, name epic.md and summarize the epic plan briefly.
  • End with exactly one explicit choice prompt:
  • approve current artifact
  • request changes
  • continue to the next spec
  • Treat continue to the next spec as approval of epic.md.
Compartilhar X LinkedIn