How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/venhdev/zenforge --skill track-tasksBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
track-tasks — Task Persistence & Lifecycle Synchronization
Operating Invariants
- Storage Exclusivity: Mutate task records exclusively in the configured tracker from
.agents/task-tracker.md(Local Markdown.agents/tasks/, GitHub Issues, GitLab, or Linear); never touch production code. - State Integrity: Maintain canonical states:
ready,in-progress,done. Treatblockedas a derived state based on prerequisite tasks; a task is onlyreadywhen all predecessor dependencies aredone. - Idempotent Synchronization: Check existing issues/files before creating; re-read after writing to verify IDs and persistence.
- Self-Contained Payloads: Embed acceptance criteria, verification commands, and inline proof into task bodies so subagents execute independently without local scratch dependencies.
- Completion Purge: Delete
.agents/tasks/<feature-slug>/(or close remote tickets) once all tasks reachdoneand verified. - Adaptive Invocation Output: Render a persistence summary table for humans; emit a compact micro-token for autonomous runners.
Domain Rubric
1. Tracker Resolution
Read .agents/task-tracker.md. If absent, stage local Markdown storage under .agents/tasks/<feature-slug>/ using <NN>-<slug>.md naming conventions (via references/issue-tracker-local.md). Honor remote tracking (gh, glab, Linear) when authenticated CLI access is confirmed. When formatting task bodies, adhere to references/task-template.md.
2. State & Task Lifecycle Transitions
STAGED: Tasks partitioned and ready for persistence authorization.DONE: Tasks verified persisted in tracker storage; implementation remains pending.UNRESOLVED: Tracker communication failure or missing authorization.
Canonical Output Contract
# Task Persistence: <Feature / Scope> · <STAGED | DONE | UNRESOLVED>
Tracker Backend: <Local Markdown | GitHub | GitLab | Linear>
Target Collection: <Path or Project Name>
| Slice ID | System Ref | Persisted Status | Blocked By | Verification Checksum |
| :--- | :--- | :--- | :--- | :--- |
| S-01 | .agents/tasks/auth/01-token.md (#102) | ready | None | <hash or pass> |
| S-02 | .agents/tasks/auth/02-refresh.md (#103) | ready (blocked) | S-01 | PENDING |
Sync Delta: <C> created, <U> updated, <D> unchanged.
*(omit if clean)* Gap: <Tracker communication failure or missing credentials.>Autonomous Micro-Token Contract:
SYNCED | tracker: <backend> | created: <C> | updated: <U> | ready: <ID>Routing
- Persistence verified and immediate implementation of eligible task authorized → (via /forge).
- Requirements conflict prevents reliable recording → (via /clarify).
- Tracker credentials missing or service unreachable → Report UNRESOLVED.
Execution Protocol
- Read
.agents/task-tracker.mdto identify the active persistence target. - Ingest Task DAG manifest from
/split-tasksor caller. - Check for existing tasks to avoid duplicate tickets.
- Write task files or call tracker APIs, embedding verification commands and parent provenance.
- Re-read stored tasks to confirm persistence, then output Markdown table or autonomous micro-token.