mcpField
W
working-on

working-on

github.com/posit-devAgent workflows551503 installsUpdated today
Repository

About working-on

working-on is a skill for maintaining a task or feature tracking document as the authoritative record. It prompts agents to record decisions, discoveries, plans, and significant work, while keeping untracked documents out of commits.

Key features

  1. 01Maintains a living tracking document
  2. 02Records decisions and new issues
  3. 03Stores plans and implementation progress
  4. 04Avoids committing untracked documents

Use cases

  1. 01Keeping task context current during implementation
  2. 02Recording decisions and newly discovered edge cases
  3. 03Reviewing tracking notes before committing

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/posit-dev/skills --skill working-on

After installing, type/working-onin Claude Code to confirm it loaded.

Details

From the project README

Working On

You are managing a tracking document that serves as the source of truth for the current task or feature.

The tracking document is: $path

Behavior

Once activated, treat the tracking document as a living record. Update it after:

  • Any decision is made (architectural, design, scope, naming, etc.)
  • A new problem, bug, or edge case is discovered
  • A new sub-feature or requirement emerges
  • An issue is raised or resolved
  • Any significant implementation work is completed
  • A key part of a conversation with the user that would be useful to recall later
  • Any time you commit files — a commit is a strong signal that the tracking document should also be reviewed and updated
  • Any plan you form — write it to the document rather than presenting it only in chat; the document is the persistent record

If in doubt, update the document. It is better to over-document than to lose context.

Git Handling

Do NOT commit the tracking document unless it already appears in the repository's git history. If the file is not tracked by git, leave it out of any commits.

Guidelines

  • Keep updates concise — bullet points and short paragraphs are preferred over prose
  • Use timestamps or date headers when the document spans multiple sessions
  • Record the why behind decisions, not just the what
  • When a section becomes stale or irrelevant, move it to an "Archive" or "Resolved" section rather than deleting it
  • If the document doesn't exist yet, create it with a sensible structure based on the task at hand

Comments

Markdown supported