implementation-tracker

Track implementation progress across work sessions in a markdown document.

8|1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/bordenet/superpowers-plus --skill implementation-tracker-bordenet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementation-tracker
Source: https://github.com/bordenet/superpowers-plus/tree/main/skills/engineering/implementation-tracker
Command: npx skills add https://github.com/bordenet/superpowers-plus --skill implementation-tracker-bordenet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large engineering issues often span multiple work sessions, causing loss of context, decisions, and progress details. This skill maintains a living progress document to capture work, decisions, refinements, and findings.

Core Features & Use Cases

  • Automatic document creation when a writing plan completes or on manual trigger.
  • Session resume loads existing progress, summarizes status, and lets the user continue.
  • Verification steps run git diff, file existence checks, symbol searches, TypeScript compile, and relevant tests after each update.
  • Auto‑condensing reduces document size and highlights red flags such as stale wiki context or mismatched git changes.
  • Integration with the writing-plans skill for seamless workflow chaining.

Quick Start

Ask the assistant to start the implementation‑tracker for issue PREFIX‑1234 to create and maintain its progress document.

Frequently Asked Questions about implementation-tracker

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

FAQPage Schema
How do I track implementation progress across multiple engineering sessions?

Tracking implementation progress across sessions involves maintaining a living markdown document that logs tasks, decisions, and verification results, automatically updating and condensing context after each work session.

How does automatic progress verification work during software engineering tasks?

Automatic progress verification executes git diff, file existence checks, symbol searches, TypeScript compilation, and relevant tests after each document update to validate the current engineering state.

When do I need a living progress document for large engineering issues?

You need a living progress document when large engineering issues span multiple days or iterations, preventing the loss of context, decisions, and progress details between work sessions.

Can I resume an engineering work session and load previous implementation context?

Yes, you can resume an engineering work session by loading an existing progress file, which summarizes the current status and allows you to continue implementation from where you left off.

How do I condense progress tracking documents to highlight stale engineering context?

Auto-condensing reduces the markdown document size and highlights red flags such as stale wiki context or mismatched git changes to keep the tracking file manageable and accurate.

Does the implementation tracker integrate with writing plans for engineering workflows?

Yes, the implementation tracker integrates with writing-plans to chain workflows, automatically creating the progress document when a writing plan completes or upon manual trigger.