Skip to main content

pv

A command-line tool for viewing and editing plan.json task tracking files.

Installation

uv tool install plan-view

Quick Start

# Create a new plan
pv init "My Project"

# Add phases and tasks
pv add-phase "Setup" --desc "Initial configuration"
pv add-task 0 "Initialize repository" --agent github-git-expert

# Track progress
pv start 0.1.1
pv done 0.1.1

# View status
pv current

Commands

View

Command Description
pv Full plan overview
pv current Current phase and next task
pv next Next actionable task
pv phase Current phase details
pv get <id> Show task or phase by ID
pv last Recently completed tasks
pv future Upcoming tasks (actionable first)
pv summary Progress summary
pv bugs Show bugs phase
pv deferred Show deferred phase
pv ideas Show ideas phase
pv validate Validate against schema

Edit

Command Description
pv init <name> Create new plan.json
pv add-phase <name> Add a phase
pv add-task <phase> <title> Add a task
pv done <id> Mark completed
pv start <id> Mark in progress
pv block <id> Mark blocked
pv skip <id> Mark skipped
pv defer <id> [-r reason] Move to deferred (with optional reason)
pv bug <id> Move to bugs
pv idea <id> Move to ideas
pv set <id> <field> <value> Set task field
pv rm task <id> Remove task
pv rm phase <id> Remove phase
pv compact Archive completed tasks to backup

Options

Option Description
-f, --file Specify plan file path
--json JSON output (view commands)
-q, --quiet Suppress output (edit commands)
-d, --dry-run Preview changes without saving

Example Output

$ pv -f examples/simple.json current

API Backend v1.0.0
Progress: 40% (2/5 tasks)

Phase 0: Setup (100%)
Phase 1: Core Features (0%)
   Create user authentication
   Build REST API endpoints

Next: [1.1.1] Create user authentication

JSON Output

All view commands support --json for programmatic access:

$ pv next --json
{
  "id": "1.1.1",
  "title": "Create user authentication",
  "status": "in_progress",
  "phase_id": "1",
  "phase_name": "Core Features",
  "agent_type": "python-backend-engineer",
  "depends_on": ["0.1.2"]
}

Features

  • Automatic progress calculation
  • Dependency-aware task ordering
  • Partial task ID matching (pv done 1 matches 1.1.1 if unique)
  • Schema validation
  • NO_COLOR/FORCE_COLOR environment variable support
  • Dry-run mode for previewing changes

Documentation

See the full documentation for detailed usage.

License

MIT

Metadata

Release files for plan-view 1.5.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for plan-view 1.5.1
File Size Uploaded Provenance Actions
plan_view-1.5.1.tar.gz 40.0 kB With provenance Details for plan_view-1.5.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for plan-view 1.5.1
File Interpreter ABI Platform Actions
plan_view-1.5.1-py3-none-any.whl Python 3 none any Details for plan_view-1.5.1-py3-none-any.whl

Total release size: 81.4 kB

Release files / plan_view-1.5.1.tar.gz

Download URL plan_view-1.5.1.tar.gz
Size 40.0 kB
Tags Source
SHA-256 checksum
How to use checksums
0af03f45ac621c2184890ee8bf4a2ecfa3463d659e303d8762e050588c9155d3
BLAKE2b-256 checksum
How to use checksums
78cbd8c57565973b78bc91ed3523b82f5581b20872369451c20656fa0a8bfa39
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release files / plan_view-1.5.1-py3-none-any.whl

Download URL plan_view-1.5.1-py3-none-any.whl
Size 41.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9be6b54a4a96a9c801b22dc73a6ae024217562834f4ce5ada84e222404f38fb8
BLAKE2b-256 checksum
How to use checksums
16b74f7bb0decfbc9d807f4b7fbf8e48178bb8e5a5deb57b03ccc5e6fdb2c0c0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Security for plan-view 1.5.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for plan_view-1.5.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page