All PAPI tools

Initialise PAPI for your project. Generates a Product Brief, seeds Active Decisions, and scaffolds workflow instructions. Run once per project after installing.

Single-call session orientation. Returns your current cycle, task counts by status, velocity snapshot, and recommended next action.

Generate BUILD HANDOFFs for the next cycle. Two-phase: prepare assembles context and returns a planning prompt, apply writes the results. PAPI selects and scopes tasks based on your backlog, active decisions, and velocity history.

List cycle tasks with their BUILD HANDOFFs ready for execution. Shows In Progress first, then Backlog.

Show the full BUILD HANDOFF for a specific task — scope, acceptance criteria, relevant files, and effort estimate.

Start or complete a build task. Call once to start (creates a feature branch, returns handoff). Call again with a build report to complete (records effort, surprises, discovered issues, and creates a PR).

Cancel a build task with a reason. Moves it back to backlog.

Capture an idea, improvement, or bug as a Backlog task for the next cycle's plan to triage. Doesn't interrupt the current cycle.

Report a bug as a prioritised Backlog task. Severity determines the priority assigned.

Record quick work done outside the normal cycle — no branch, no PR, just a log entry. Keeps your cycle history accurate.

List tasks waiting for review — those that have been built but not yet accepted.

Record your verdict on a completed build. Accept merges the PR and marks the task Done. Request-changes sends it back. Reject cancels it.

Cut a versioned release — creates a git tag, generates a CHANGELOG entry, and pushes to remote.

View the task board with optional filters by status, priority, or module.

Move a task out of the current cycle back to backlog. Use this to adjust scope mid-cycle without cancelling.

Archive Done or Cancelled tasks to keep the board focused on active work.

Detect and fix board state mismatches — orphaned branches, missed completions, status drift between git and the board.

Run a strategy review — assesses Active Decisions, velocity, and project direction. Two-phase: prepare returns the review prompt, apply saves the results with recommendations for the next plan.

Capture a strategic direction change as a new or updated Active Decision — with reasoning, evidence, and confidence level.

Step back and get a high-level view of project direction, horizon progress, and strategic alignment.

Update your project's horizon, stage, or phase structure — reflecting meaningful shifts in project scope or direction.

Register a research or planning document in the doc registry. Stores metadata, a structured summary, and any actionable findings — not the full content.

Search the doc registry by type, tags, keyword, or pending actions. Returns summaries for context gathering.

Scan your docs directory for markdown files not yet registered in the registry.