pipa-define-work

pipa-define-work is a skill for Claude Code, Codex from lunchpaillola/pipa-skills. It costs 48 tokens per session (736 once invoked), scanned A, original, MIT.

A routing skill that turns a vague business request into one focused type of defined work, such as requirements, scope, stakeholders, or a roadmap.

In plain words
What is it for?
It helps frame problems, map stakeholders, create project charters, write requirements, set scope, plan roadmaps, record decisions, and prepare a workday plan.
Why use it?
Choosing one clear planning operation prevents a broad request from becoming an unfocused collection of documents.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps frame problems, map stakeholders, create project charters, write requirements, set scope, plan roadmaps, record decisions, and prepare a workday plan.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lunchpaillola/pipa-skills/pipa-define-work
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add lunchpaillola/pipa-skills --skill pipa-define-work
Clone the repo
git clone --depth 1 https://github.com/lunchpaillola/pipa-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for pipa-define-work

README.md
[![agentmods](https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-define-work/github.svg)](https://agentmods.dev/skills/lunchpaillola/pipa-skills/pipa-define-work)
Your own site
<a href="https://agentmods.dev/skills/lunchpaillola/pipa-skills/pipa-define-work"><img src="https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-define-work/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for pipa-define-work

Your own site · 80×15
<a href="https://agentmods.dev/skills/lunchpaillola/pipa-skills/pipa-define-work"><img src="https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-define-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 736 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.00736
Opus 5 $0.00024 $0.00368
Sonnet 5 $0.00010 $0.00147
Haiku 4.5 $0.00005 $0.00074

Measured 12d ago against content hash 57781b026b32, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

pipa-define-work scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/pipa-define-work/SKILL.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pipa Define Work

Route fuzzy demand to one focused Define Work operation.

When present, read ~/.pipa/profile.md once for durable business context. If missing, continue without blocking and do not start setup unless the user asks or a soft setup offer is useful.

Select One Operation

Explicit operation invocation wins. Otherwise select exactly one primary operation and preserve the user's business objective:

  • pipa-problem-framing: clarify the problem, affected people, desired outcomes, success criteria, constraints, or non-goals.
  • pipa-stakeholder-map: map stakeholders, RACI roles, decision authority, approvals, communication, or escalation paths.
  • pipa-project-charter: assess charter readiness and make a go, go-with-conditions, or no-go viability decision.
  • pipa-requirements-brief: turn notes or a broad project-planning ask into requirements, acceptance boundaries, and unresolved decisions.
  • pipa-scope-baseline: baseline deliverables, exclusions, milestones, schedule assumptions, tolerances, and change triggers.
  • pipa-roadmap: sequence candidate work into now/next/later or another requested prioritization method.
  • pipa-decision-log: set up RAID, RACI, decision records, ownership, and review cadence.
  • pipa-daily-plan: brief one specific workday around due work, active priorities, goals, and calendar commitments.

Tie-Breakers

  • “Plan this project” or similarly broad project planning selects pipa-requirements-brief, not pipa-daily-plan.
  • Select pipa-daily-plan only when one specific workday's priorities are central. Incidental today wording does not override project requirements, scope, milestone, or roadmap intent.
  • Recurring or scheduled Daily Plan setup goes to pipa-manage.
  • Start-readiness or go/no-go intent selects pipa-project-charter; problem clarity selects pipa-problem-framing.
  • Ownership of the engagement selects pipa-stakeholder-map; governance controls across workstreams select pipa-decision-log.
  • Defining acceptance criteria, checks, or boundaries selects pipa-requirements-brief; assessing delivered work for final acceptance, approval, or signoff goes to pipa-improve-operations.
  • If multiple operations apply, run the one needed first and name the others only as follow-ups.

Read the full file on GitHub · 52 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 52 lines · 48 tokens per session scan A 57781b026b32

Subscribe to this mod's changes

pipa-define-work is a skill published in the GitHub repository lunchpaillola/pipa-skills (3 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 736 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

autoresearch

Autonomously optimize any Claude Code skill by running it repeatedly, scoring outputs against binary evals, mutating the prompt, and keeping improvements. Based on Karpathy's autoresearch methodology. Use when: optimize this skill, improve this skill, run autoresearch on, make this skill better, self-improve skill…

lunchpaillola/lola-opencode · 100 tokens

obsidian-bases

Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.

lunchpaillola/lola-opencode · 63 tokens

json-canvas

Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.

lunchpaillola/lola-opencode · 54 tokens

obsidian-markdown

Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

lunchpaillola/lola-opencode · 71 tokens

compound

Capture and compound learnings from conversations into reusable commands and skills through interactive dialogue.

lunchpaillola/lola-opencode · 17 tokens

obsidian-cli

Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their…

lunchpaillola/lola-opencode · 102 tokens