Receber por email
← Voltar para o catálogo

ralph-specum-status

This skill should be used only when the user explicitly asks to use `$ralph-specum-status`, or explicitly asks Ralph Specum in Codex for status or active spec progress.

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

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 Status

Use this to report Ralph state across configured spec roots.

Contract

  • Read .claude/ralph-specum.local.md when present
  • Default specs root is ./specs
  • .current-spec lives in the default specs root
  • Hidden directories do not count as specs

Action

  1. Resolve configured roots.
  2. Read .current-spec to identify the active spec.
  3. If .current-spec is missing or empty, report that there is no active spec and continue listing specs across roots.
  4. Read specs/.current-epic when present and summarize epic status.
  5. For each spec directory, inspect:
  6. .ralph-state.json
  7. research.md
  8. requirements.md
  9. design.md
  10. tasks.md
  11. If tasks.md exists, count completed and incomplete tasks.
  12. Group results by spec root.
  13. Show the active spec, current phase, backlog state, approval state, granularity when present, and which artifacts exist.

Output

  • Specs in the default root can be shown by name.
  • Specs in other roots should include the root suffix for disambiguation.
  • Include the next likely command when it is obvious.
  • If an epic is active, include the next unblocked spec.
  • If approval is pending, explicitly tell the user to approve the current artifact, request changes, or continue to the named next step.
Compartilhar X LinkedIn