actions

Log actions against briefs and track weekly progress in centralized files.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/benhuds/pm-os --skill actions-benhuds
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: actions
Source: https://github.com/benhuds/pm-os/tree/main/.claude/skills/actions
Command: npx skills add https://github.com/benhuds/pm-os --skill actions-benhuds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams need a reliable way to record actions taken against briefs, track weekly progress, and review open items to demonstrate progress and accountability.

Core Features & Use Cases

  • Weekly Action Tracker in actions/ where each week has one file: actions/week-YYYY-MM-DD.md.
  • From Brief auto-generates action items, and /actions log appends entries.
  • Commands supported include log, list, carryover, and the interface ties into the friction log for visibility.

Quick Start

Run the /brief command to generate this week’s actions, then use /actions log to record entries.

Frequently Asked Questions about actions

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

FAQPage Schema
How do I log actions and track weekly progress for product briefs?

To log actions and track weekly progress, run the /brief command to auto-generate action items, then use /actions log to append entries into a centralized weekly file named actions/week-YYYY-MM-DD.md.

What is the best way to auto-generate action items from existing briefs?

Auto-generating action items from briefs uses the /brief command, which extracts tasks and populates the weekly actions file, providing a structured recap of daily updates and ongoing open items.

Can I track carryover actions from previous weeks in a centralized log?

Yes, tracking carryover actions is supported through the list and carryover commands, which review open items from prior weekly files and roll them into the current week for accountability.

Does this weekly action tracker integrate with a friction log?

The weekly action tracker integrates directly with the friction log interface, tying logged actions and open items into friction entries to provide visibility into project blockers and progress.

What file format is used for the weekly action tracker?

The weekly action tracker uses markdown files stored in the actions/ directory, creating one file per week formatted as actions/week-YYYY-MM-DD.md to centralize daily updates and recaps.

How do I list open actions for the current project cycle?

Listing open actions for a project cycle uses the list command within the weekly tracker, pulling all logged and auto-generated entries from the current week's markdown file for review.