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 1matches1.1.1if 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
Release files for plan-view 1.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| plan_view-1.5.0.tar.gz | 38.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| plan_view-1.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 79.9 kB
Release files / plan_view-1.5.0.tar.gz
| Download URL | plan_view-1.5.0.tar.gz |
|---|---|
| Size | 38.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd2c479d92a7a969f4b1ea1747420bc985886a14f4c5f8e77c922635b0ee3592
|
|
BLAKE2b-256 checksum How to use checksums |
beb7f95b74eb259926a7835fe6fd0a85ee46fd058ac8d69a322f216b680d24fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 16, 2026.
Transparency logRelease files / plan_view-1.5.0-py3-none-any.whl
| Download URL | plan_view-1.5.0-py3-none-any.whl |
|---|---|
| Size | 41.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dbbf864602afd47e1edc6a61798146c8fdb5365abea6725780691abe0e3c7be7
|
|
BLAKE2b-256 checksum How to use checksums |
62bb9a4bb658b8325834341141729f581b22629b58d2c4f5caee688718ba2d53
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 16, 2026.
Transparency log