how-far

Compare codebase implementation against a destination document and report statuses with evidence.

5|4|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/haakonbull/autosprint --skill how-far
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: how-far
Source: https://github.com/haakonbull/autosprint/tree/main/.claude/skills/how-far
Command: npx skills add https://github.com/haakonbull/autosprint --skill how-far

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a fast, scannable overview of how much of the autosprint/destination.md has been implemented in your codebase, helping you understand the remaining distance to the target state.

Core Features & Use Cases

  • Estimate Progress: Reports the status of each requirement in destination.md as done, partial, not started, or unclear.
  • Code Evidence: Provides evidence for each status, including file references and test coverage.
  • Use Case: Use when you need to quickly understand what parts of your codebase are complete and what remains to be done.

Quick Start

Run the 'how-far' skill to get a snapshot of your codebase's progress towards autosprint/destination.md.

Frequently Asked Questions about how-far

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

FAQPage Schema
How do I track codebase implementation progress against project requirements?

To assess codebase progress, parse a destination document for requirements and scan source files with tests for evidence. This process reports each requirement's status as done, partial, not started, or unclear with file references.

What is the best way to generate a status report for remaining development tasks?

Generating a status report for remaining tasks requires parsing a destination document for requirements and matching them with codebase evidence. This yields a scannable overview classifying each item as done, partial, not started, or unclear.

How does code evidence matching work for requirement status tracking?

Code evidence matching for requirement tracking works by parsing a destination document for requirements and scanning the codebase for source and test evidence. It then maps file references and test coverage to classify implementation status.

Do I need a destination.md file to measure codebase completion status?

You need a destination.md file to measure codebase completion status because the Skill parses this document for requirements. It then matches these requirements against source code and test coverage to report progress.

Can I use progress tracking for codebases with partial test coverage?

Progress tracking works with partial test coverage by evaluating available source and test evidence to classify requirements. Items lacking sufficient evidence are reported as unclear or partial rather than fully done.

Why does my requirement status show as unclear during codebase progress tracking?

A requirement status shows as unclear during codebase progress tracking when the Skill cannot find sufficient source or test evidence in the codebase to confidently classify the implementation as done, partial, or not started.