estado-projeto

Maintains resumable project task state in a JSON state file with a regenerated Markdown view.

1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/codjeremias-cell/Orquestrador-fable --skill estado-projeto-codjeremias-cell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: estado-projeto
Source: https://github.com/codjeremias-cell/Orquestrador-fable/tree/main/skills/estado-projeto
Command: npx skills add https://github.com/codjeremias-cell/Orquestrador-fable --skill estado-projeto-codjeremias-cell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI assistants do not remember between sessions, and large projects do not fit in one. This Skill gives a project a durable, resumable task state: where each task stands, what it produced, and what comes next, so any session can pick up exactly where the last one stopped. ## Core Features & Use Cases - Single source of truth: an estado.json state machine (one entry per task with status, priority, artifacts, and optional blocking edges) from which a human-readable TAREFAS.md view is deterministically regenerated. - Controlled status transitions: a canonical 9-status enum (nao_iniciada through concluida/abandonada) with validated transitions, safe writes via backup plus atomic temp-file rename, and concurrent-write detection through atualizado_em checks. - Orchestration support: stores round counters, scoreboards with per-lens granularity, pinned success predicates with fail-closed revalidation, and write-once execution receipts for iterative loops. - Use Case: You return to a project after several days and ask where things stopped. The Skill reads estado.json, reports each task's status, and resumes work without reconstructing context. ## Quick Start Ask the assistant to read the project state and tell you where each task stopped and what to do next.

Frequently Asked Questions about estado-projeto

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume a project across multiple AI chat sessions?▼

Keep a persistent task state file that records each task's status, artifacts, and next step. At the start of a new session, load the state file and continue from the recorded position instead of reconstructing context from conversation history.

How do I track task status in a project managed by an AI assistant?▼

Use a state machine with a canonical status enum such as not started, researching, planned, implementing, blocked, and done. Validate every transition before applying it, and regenerate any human-readable task list from the machine-readable source so the two never diverge.

What is the difference between project state and project memory?▼

State tracks where each task stands right now: status, progress, and next steps, and it ages quickly. Memory stores durable preferences, decisions, and lessons about how the team works. Items that expire within a week belong in state, not memory.

How do I safely write a JSON state file without corruption?▼

Create a backup copy first, write to a temporary file in the same directory, then atomically rename it over the original. Check a last-updated timestamp before overwriting to detect concurrent writes, and regenerate derived views only after the source is safely saved.

When should I not create a persistent task state file?▼

Skip it for one-off work that fits in a single session, since the ceremony has no owner. Only create the state when work will continue in a future session or when an orchestrator needs to resume multi-round execution.