70-close-task-150

Enforce single accurate task statuses with artifact validation and lifecycle transitions.

Updated Jan 30, 2025
One-click install
npx skills add https://github.com/MykhailoDmytriakha/my-preacher-helper --skill 70-close-task-150
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 70-close-task-150
Source: https://github.com/MykhailoDmytriakha/my-preacher-helper/tree/main/.codex/skills/70-close-task-150
Command: npx skills add https://github.com/MykhailoDmytriakha/my-preacher-helper --skill 70-close-task-150

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that every task has a single, accurate status and that artifacts consistently prove completion, preventing duplicates and cross-system inconsistencies.

Core Features & Use Cases

  • One-to-one status tracking: ensures a single authoritative status for each task.
  • Artifact alignment: verifies deliverables match the claimed status.
  • Duplicate prevention: detects and eliminates tasks appearing in multiple places.
  • Lifecycle enforcement: governs valid state transitions and audit trails.

Quick Start

Update a task by progressing its status and validating artifacts to maintain a single source of truth.

Frequently Asked Questions about 70-close-task-150

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

FAQPage Schema
How do I enforce a single accurate status for each task in my workflow?

Task lifecycle coordination enforces a single authoritative status for each task by governing valid state transitions and preventing duplicates. It validates artifact alignment to ensure deliverables consistently prove the claimed completion status.

What is the best way to prevent duplicate tasks across cross-system tracking artifacts?

Duplicate prevention detects and eliminates tasks appearing in multiple places by maintaining a single source of truth. It ensures cross-system consistency by verifying that artifacts match the single authoritative task status without duplication.

How do I validate that task artifacts match the claimed progress status?

Artifact alignment verifies deliverables match the claimed status by applying defined transitions and logging. It ensures task artifacts consistently prove completion, preventing misaligned outputs from progressing through the lifecycle.

How does lifecycle enforcement govern valid state transitions for task tracking?

Lifecycle enforcement governs valid state transitions by applying defined rules and audit trails to task tracking. It maintains auditability through logging, ensuring every status update follows authorized state changes and prevents misaligned artifacts.

When do I need auditability and defined transitions for task status updates?

Auditability and defined transitions are needed when managing task lists, progress updates, and cross-system tracking to prevent duplicates. They satisfy requirements for status correctness by logging authorized state changes and verifying artifact completion.

Can I apply one-to-one status tracking to existing task lists and progress updates?

One-to-one status tracking applies directly to existing task lists and progress updates to establish a single source of truth. It updates task statuses by validating artifacts and enforcing lifecycle transitions without requiring new infrastructure.