Skill

effort-log

Log progress on an effort. Use when the user says "log this", "here's what I did", "update effort", or after completing meaningful work on a tracked effort. Writes to both the effort's

Install

npx claudepluginhub acjackman/claude-productivity

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Records progress on a specific effort in two places: the effort file (permanent record) and today's daily note (daily context).

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

158.9k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

158.9k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

158.9k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 22, 2026

Actions

View Source View Plugin View on GitHub View README

Effort Log

Records progress on a specific effort in two places: the effort file (permanent record) and today's daily note (daily context).

Arguments

$ARGUMENTS describes the progress. May reference an effort by name, slug, or wikilink.

Instructions

Identify the effort:

Parse $ARGUMENTS for effort references (wikilinks, slugs, titles)
If ambiguous, check memory/AGENTS.md active efforts
If still ambiguous, ask: "Which effort? I see: ..."
Read the effort file to understand current state

Extract progress details:

What was done (bullets)
Any decisions made
What's next (if mentioned)
Links (PRs, Slack threads, docs)

Write to the effort's ## Log via patch_note:

### YYYY-MM-DD
- What was accomplished
- Decisions or findings
- [Link to PR](url)

Append after existing log entries. Create ## Log section if it doesn't exist.

Write to today's daily note ## Log via log_entry:

log_entry({
  description: "Progress on <Effort Title>",
  bullets: ["summary of what was done", "links"],
  date: "YYYY-MM-DD"
})

Update effort if appropriate:

If progress suggests a status change (e.g., "finished" → done, "waiting on review" → waiting), suggest it but don't auto-change
If the user mentions next steps not already in the effort, suggest adding them

Confirm:

Logged progress on Phoenix DB Migration:

Effort: added to ## Log (2026-03-22)

Daily: logged at 14:30

When called without arguments

If no arguments, ask:

What effort did you make progress on? What did you do?

Effort Log

Records progress on a specific effort in two places: the effort file (permanent record) and today's daily note (daily context).

Arguments

$ARGUMENTS describes the progress. May reference an effort by name, slug, or wikilink.

Instructions

Identify the effort:
- Parse $ARGUMENTS for effort references (wikilinks, slugs, titles)
- If ambiguous, check memory/AGENTS.md active efforts
- If still ambiguous, ask: "Which effort? I see: ..."
- Read the effort file to understand current state
Extract progress details:
- What was done (bullets)
- Any decisions made
- What's next (if mentioned)
- Links (PRs, Slack threads, docs)
Write to the effort's ## Log via patch_note:
```
### YYYY-MM-DD
- What was accomplished
- Decisions or findings
- [Link to PR](url)
```
Append after existing log entries. Create ## Log section if it doesn't exist.

Write to today's daily note ## Log via log_entry:

log_entry({
  description: "Progress on <Effort Title>",
  bullets: ["summary of what was done", "links"],
  date: "YYYY-MM-DD"
})

Update effort if appropriate:
- If progress suggests a status change (e.g., "finished" → done, "waiting on review" → waiting), suggest it but don't auto-change
- If the user mentions next steps not already in the effort, suggest adding them
Confirm:
Logged progress on Phoenix DB Migration:
- Effort: added to ## Log (2026-03-22)
- Daily: logged at 14:30

When called without arguments

If no arguments, ask:

What effort did you make progress on? What did you do?