Plan

Structured non-code project and knowledge management for Claude Code. (Before Karpathy made this fashionable...)

Install

npx -y skills add OdinMB/ops-workflow --skill plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create an ops work plan for a new task. Proposes steps and success criteria for user approval before execution.

SKILL.md

2.8 KB, as published. Nobody here has run it

Create a work plan for the following task: $ARGUMENTS

Instructions

Research first. Read MEMORY.md, backlog/INDEX.md, and any relevant state/ or references/ files to understand current state and prior work. Check plans/completed/ for related past tasks. Check backlog/ for an existing draft plan that matches this task.
Create or activate the plan file. If a draft plan exists in backlog/, move it to plans/, update its date to today, and set status to active. Refine the plan based on your research. If no draft exists, write a new file at plans/YYYY-MM-DD-<slug>.md where the slug is a short kebab-case name derived from the task. Use today's date. Use this format:

# Task: <Descriptive Name>

- **Date**: YYYY-MM-DD
- **Status**: active

## Objective
What we're trying to accomplish and why. Be specific.

## Plan
1. Step one
2. Step two
3. ...

**Artifacts:** Where deliverables will be stored (e.g. `artifacts/`, `artifacts/<subfolder>/`).

**Files to create/modify:** List every file and folder expected to be created, moved, or significantly changed — including which `INDEX.md` files will need updating.

**Success criteria:**
- [ ] Criterion A
- [ ] Criterion B

Leave the sections below the plan blank — they get filled in during and after execution:

## Outcome
_Fill in when completed._

## Key Decisions
_Fill in when completed._

## Artifacts
_Fill in when completed._

## Session Log
_Fill in when completed._

Present and clarify. Summarize the objective, proposed steps, and success criteria. Then surface any scope decisions, trade-offs, or assumptions that need user input. Use the AskUserQuestion tool with concrete options — don't ask open-ended questions when specific choices are available. Group related decisions (up to 4 per question). If the task produces artifacts (copy, drafts, deliverables), clarify where they should be stored if not obvious (default: artifacts/). Skip clarification if the task is absolutely straightforward. Update the plan file with the user's answers. Wait for approval before any work begins.
Do NOT execute the plan. This skill only creates and proposes the plan. Execution happens via the /execute skill after the user approves.
Scope check. Plans in non-code repos must never include implementing code changes. This workflow produces content, research, specs, and briefs — not code. If a task involves building something in an app, the plan should cover producing the content/spec/brief that the user takes to the coding repo.

One thing to look at

What its author says it does

SKILL.md

Instructions

Keep looking