Geraldo Neto
Community@GeraldoNeto123
Geraldo Neto maintains skills for ticket-queue orchestration, shared-state modeling gates, and commit-interval consistency checkpoints in spec-driven development.
Agent Skills by Geraldo Neto
Showing 3 vetted skills indexed across 1 GitHub repositories.
GeraldoNeto123checkpoint
Reviews accumulated ticket implementations across commit intervals for cross-session consistency defects.
GeraldoNeto123estado-compartilhado
Maps shared state writers across flows and resolves writer conflicts into ADRs before ticket slicing.
GeraldoNeto123run
Orchestrates a feature's ticket queue with one fresh subagent per ticket.
Frequently Asked Questions About Geraldo Neto
FAQPage SchemaWhat tasks can I perform using Geraldo Neto's skills?▼
You can orchestrate a feature's ticket queue with a fresh subagent per ticket, run consistency checkpoints over commit intervals every 5 closed tickets, and model shared state between specification and ticket slices while resolving writer conflicts in an ADR.
Who are these skills designed for?▼
These skills target developers practicing spec-driven, ticket-based development who decompose features into slices. They suit engineers coordinating multi-ticket implementations that require shared-state modeling, writer-conflict resolution, and periodic consistency review of accumulated work.
How does the checkpoint skill run in practice?▼
The checkpoint skill is invoked automatically by the /ticket:run orchestrator every 5 closed tickets, or manually by the user to review accumulated work from manual sessions. It dispatches the checkpoint-reviewer agent over a defined commit interval.
What are the prerequisites and dependencies for these skills?▼
The skills depend on a ticket-based workflow with /to-spec, /to-tickets, and /ticket:run commands. The run and estado-compartilhado skills have model invocation disabled, and checkpoint requires the checkpoint-reviewer agent to perform consistency reviews.
How does estado-compartilhado handle state conflicts?▼
Estado-compartilhado acts as a modeling gate between /to-spec and /to-tickets. It maps the state that feature slices will share and resolves writer conflicts by recording decisions in an ADR, preventing overlapping writes across tickets.