agentleFS
Sign inStart free
getpapigetpapi/papi/skills/papi-strategy/SKILL.md

papi-strategy

Skill11 starsChanged 3 months agoMITView on GitHub

Invoke when running strategy_review or making Active Decision changes. Covers strategy review cadence and AD lifecycle.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every 5 cycles, PAPI offers a strategy review — a deep analysis of velocity, estimation accuracy, active decisions, and project direction.

    line 10
  2. Distinctive:

    Run in the current conversation.

    line 13
  3. Very specific:

    If the review recommends AD changes, use strategy_change to apply them.

    line 16
  4. Distinctive:

    After apply, verify the stored review and recommendations.

    line 20
  5. Very specific:

    Check ADs before making architectural choices — run health for the AD summary.

    line 31
  6. Very specific:

    When new evidence appears, update AD confidence via strategy_change.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

papi-strategy

Strategy Reviews

Every 5 cycles, PAPI offers a strategy review — a deep analysis of velocity, estimation accuracy, active decisions, and project direction.

  • Don't skip them. They're where compounding value comes from.
  • Run in the current conversation. Only verified context pressure warrants a fresh chat; elapsed time, task type and compaction alone do not.
  • Reviews produce recommendations that feed into the next plan.
  • If the review recommends AD changes, use strategy_change to apply them.

Close the review

After apply, verify the stored review and recommendations. Apply authorized decision changes and feed the findings into the next proposed task set. Share externally only when requested, through an available supported tool, with explicit send authorization for the destination. Marketing is not a review gate. Remote HTTP accepts inline output or supported structured chunks; a caller-local output path works only when the connected local workspace server can read it.

Active Decision Lifecycle

Active Decisions (ADs) track architectural and product choices with confidence levels (LOW → MEDIUM → HIGH).

  • Check ADs before making architectural choices — run health for the AD summary.
  • ADs are for product/architecture choices only, not process preferences.
  • When new evidence appears, update AD confidence via strategy_change.
  • Supersede rather than overwrite — old decisions stay as history.
  • An AD conflict is a user decision. Submit it through idea with conflicts_with_ad: "AD-N"; preserve its evidence behind the decision gate instead of shelving it. Use the deployment's supported resolution flow.
  • New ADs should include a ### Reversal Trigger section: specify the signal that would invalidate the stance, the action to take (modify/supersede/abandon), and why writing it now prevents sunk-cost drift later.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free