progress-doc

Create and update standardized markdown progress documents for feature branches.

5|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/f4irline/bbqparty-ai --skill progress-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: progress-doc
Source: https://github.com/f4irline/bbqparty-ai/tree/main/packages/opencode/.opencode/skills/progress-doc
Command: npx skills add https://github.com/f4irline/bbqparty-ai --skill progress-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a consistent, discoverable progress document and update workflow so developers can track feature-branch implementation status, avoid lost context after interruptions, and ensure work is ready for review and merge.

Core Features & Use Cases

  • Standardized progress document template stored in the docs/progress directory with fields for branch, worktree path, status, timestamps, overview, workflow checklist, progress log, technical notes, blockers, testing, and files changed.
  • Use cases include starting a new ticket, logging incremental progress during implementation, recording learnings, tracking blockers for coordination, and finalizing work before creating a pull request.
  • Complements git worktree workflows and points to companion skills for committing, pushing, and creating PRs so the documentation stays in sync with code changes.

Quick Start

Create or update the progress document in the docs/progress folder for your current branch, add a timestamped progress log entry, update the status and checklist, and then commit and push the changes.

Frequently Asked Questions about progress-doc

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

FAQPage Schema
How do I track feature-branch implementation progress across worktrees?

You can maintain progress documents for feature branches by creating standardized markdown files in the docs/progress directory to log status, workflow checklists, blockers, and files changed.

What is a progress document for a git worktree workflow?

A progress document for a git worktree is a standardized markdown file tracking implementation status, workflow checklists, and blockers to prevent lost context after interruptions.

How do I record progress logs and blockers during feature development?

You record progress logs and blockers by applying the document template to your branch worktree, adding timestamped entries to capture status, technical notes, and testing updates.

Does this progress tracking workflow require specific dependencies?

This progress tracking workflow requires no specific dependencies, relying only on markdown files stored under the docs/progress directory in your feature branch worktree.

When do I need to update the workflow checklist for a linear ticket?

You update the workflow checklist for a linear ticket when logging incremental progress during implementation and finalizing work before creating a pull request.

What is the best way to finalize feature-branch documentation before a pull request?

The best way to finalize feature-branch documentation is to update the status, complete the workflow checklist, verify files changed, and commit and push the progress markdown file.