estimate-hours

Log token burn and estimate human-equivalent hours to bridge/timesheet.jsonl.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/hilbertp/liberation-of-bajor --skill estimate-hours
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: estimate-hours
Source: https://github.com/hilbertp/liberation-of-bajor/tree/main/.claude/skills/estimate-hours
Command: npx skills add https://github.com/hilbertp/liberation-of-bajor --skill estimate-hours

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams need a unified way to record both the token consumption and the human‑equivalent effort for every AI‑generated deliverable, enabling clear economics, ROI analysis, and transparent retrospectives.

Core Features & Use Cases

  • Standardized logging: Append a JSON line to bridge/timesheet.jsonl with a defined schema after any significant piece of work.
  • Economic aggregation: Group entries by deliverable to compute total human hours and token burn for reporting and decision‑making.
  • Idea capture integration: Automatically runs the idea‑capture skill after each log to preserve emerging concepts.
  • Applicable scenarios: Brief creation, code implementation, design reviews, architecture decisions, planning, and any other tracked activity.

Quick Start

After finishing a task, add a timesheet entry to bridge/timesheet.jsonl following the provided schema.

Frequently Asked Questions about estimate-hours

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

FAQPage Schema
How do I log AI token costs and human hours for project deliverables?

You log token costs and human hours by appending a JSON line to bridge/timesheet.jsonl after completing significant work, using a defined schema to record time and cost metrics for each deliverable.

What is a human-equivalent hours estimation for AI generated work?

Human-equivalent hours estimation records the time a human would spend on a deliverable alongside actual token burn, enabling teams to measure economics, ROI, and effort transparently for AI-assisted tasks.

How do I track token burn for architecture decisions and design reviews?

You track token burn by applying this logging process after finishing design reviews or architecture decisions, appending cost and effort data as a structured JSON entry to your timesheet file.

Can I aggregate timesheet entries to compute total token cost for a deliverable?

Yes, you can aggregate timesheet entries by grouping JSON lines by the deliverable field, allowing you to compute total human hours and token burn for economic reporting and retrospective analysis.

Does this timesheet logging process require any external dependencies?

No, this timesheet logging process requires no external dependencies, operating by appending structured JSON lines to a local file and optionally triggering an idea-capture skill.