plan-updates

Update plan, task, and BDD spec artifacts with HITL-approved checkoffs.

2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/grimlor/universal-dev-skills --skill plan-updates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-updates
Source: https://github.com/grimlor/universal-dev-skills/tree/main/skills/plan-updates
Command: npx skills add https://github.com/grimlor/universal-dev-skills --skill plan-updates

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents progress updates from becoming inconsistent, incomplete, or unverifiable by standardizing where and how plans, tasks, and BDD specs are tracked and checked off.

Core Features & Use Cases

  • Progress tracking across workflow phases: Updates the project plan, task log, and behavioral specs after feature, refactor, bug-fix, and audit/remediation checkpoints.
  • Append-only session logging: Maintains an audit-friendly history of what changed and where work should resume without rewriting past entries.
  • Checkpoint-accurate completion rules: Requires HITL approval and real test verification before checkoffs, preventing speculative or mock-based completion.
  • Artifact placement discipline: Ensures tracking artifacts live under .copilot/ and avoids writing them to project root docs/specs/tests paths unless the user moves them.

Quick Start

Ask your AI agent to update the current progress by locating or creating .copilot/plan.md and .copilot/task.md, then check off only fully verified items after updating the corresponding BDD specs.

Frequently Asked Questions about plan-updates

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

FAQPage Schema
How do I maintain audit-ready progress tracking for tasks and BDD specs?

To maintain audit-ready progress tracking, update plan and task artifacts alongside BDD specs after each workflow phase, requiring HITL approval and verified tests before checking off completed items.

What's the best way to prevent inconsistent project plan updates across workflow phases?

Preventing inconsistent project plan updates requires standardizing artifact placement in .copilot/ directories and enforcing append-only session logging, ensuring a verifiable history of changes without rewriting past entries.

How do I enforce human-in-the-loop approval for task checkoffs in project artifacts?

Enforcing human-in-the-loop approval for task checkoffs requires real test verification and explicit HITL approval before marking items complete, preventing speculative or mock-based completion in project artifacts.

Does BDD spec governance require separate files for plans and task logs?

BDD spec governance requires disciplined artifact placement, maintaining separate plan.md and task.md files under the .copilot/ directory to keep tracking artifacts distinct from project root documentation.

Why does progress tracking fail during recurring audit checkpoints?

Progress tracking fails during recurring audit checkpoints when completion rules are not enforced, allowing items to be checked off without real test verification or HITL approval in the updated BDD specs.

Can I use append-only session logging for bug-fix workflows and refactor phases?

Append-only session logging applies to bug-fix-workflow and refactor-workflow phases, maintaining an audit-friendly history of behavioral spec changes and where work should resume without rewriting past entries.