Parpt - Project Audit & Revenue Prioritization Tool

Parpt is an interactive CLI tool that helps developers, indie creators and teams evaluate and prioritize their software projects using structured metrics like ICE and RICE.

Features

• Guided project scoring using ICE and RICE methods
• Calculate ICE (Impact, Confidence, Ease) scores
• Calculate RICE (Reach, Impact, Confidence, Effort) scores
• Export projects to Markdown and JSON formats
• Obsidian-compatible markdown export with sorting by name, any scoring field or ICE/RICE scores
• Rank and sort projects by monetization, potential, feasibility and effort
• Spring Boot architecture with interactive shell
• 100% local-first and open source (your projects never leave your machine; see Usage reporting)

Evaluation Framework

Each project is evaluated across 5 dimensions using a detailed 1-5 scoring system:

• Impact: Monetary value, user happiness, competitive advantage, problem-solving
• Confidence: Requirement clarity, team experience, skill fit, requirement stability
• Ease: Build complexity, tooling readiness, code reuse potential, testability
• Reach: User coverage, new user attraction, visibility, usage frequency
• Effort: Development time, team size, maintenance burden, ongoing work

Installation

Clone and build manually: git clone https://github.com/Stephenson-Software/Parpt.git cd Parpt ./gradlew build java -jar build/libs/Parpt-*.jar

Getting Started

Run the CLI: java -jar build/libs/Parpt-*.jar

Available commands:

• create - Create a new project with guided scoring
• list (alias: ls) - List all projects with scores, optionally sorted
• view <project-name> - View detailed project information
• delete <project-name> (alias: rm) - Delete a project by name
• export - Export all projects to Markdown format, optionally sorted
• help - Show available commands

You'll be prompted to enter:

• Project name and description
• Detailed scoring for each category (1-5 scale)
• Entering q or quit at any prompt (or pressing Ctrl-D) cancels creation without saving anything
• Parpt will then:
  • Calculate ICE and RICE scores
  • Save the results to projects.json
  • Allow you to export to projects.md sorted by priority
  • Help you sort and review your efforts over time

List Examples

# List projects in the order they were created (default)
list

# The 'ls' alias behaves identically
ls

# List projects sorted by a score, highest first
list --sort ice
list --sort rice

# List projects sorted by name (A to Z) or by any scoring field, highest first
list --sort name
list -s impact

Supported --sort values are name, impact, confidence, ease, reach, effort, ice and rice. Every value except name sorts from highest to lowest; omitting --sort keeps the order in which projects were created.

Delete Examples

# Delete a project by name
delete "My Project"

# The 'rm' alias behaves identically
rm "My Project"

Deleting a project removes it from projects.json immediately; there is no confirmation prompt and no undo. If no project has the given name, delete reports Project not found: <project-name> and nothing is changed.

Export Examples

# Export projects sorted by ICE score (default)
export

# Export projects sorted by RICE score
export --sort rice

# Export projects sorted by name (A to Z) or by any scoring field, highest first
export --sort name
export -s impact

export accepts the same --sort values as list: name, impact, confidence, ease, reach, effort, ice and rice. Every value except name sorts from highest to lowest, and the chosen order is recorded in the exported file's header. Unlike list, export always sorts — omitting --sort sorts by ICE score.

Roadmap

• Project input and validation loop
• Score calculation engine
• Markdown and JSON writer modules
• CLI configuration and persistence
• Obsidian-compatible markdown export with sorting
• Visualization of project scores
• Batch project comparison features

Usage reporting

Usage reporting is on by default: Parpt reports that it was used to the maintainers' trace service at https://trace.danielstephenson.dev, sending a startup event carrying its name and version once per run, and a project-created event carrying nothing else when a project is saved. Nothing about your projects is sent: no project names, descriptions, scores or files, and no usernames, hostnames, IP addresses, paths or anything typed at the prompt. A one-line notice is printed the first time it runs on a machine (recorded in ~/.config/parpt/usage-reporting-notice-shown).

To turn it off, any one of these is enough:

• java -Dusage-reporting.enabled=false -jar build/libs/Parpt-*.jar
• USAGE_REPORTING_ENABLED=false in the environment
• TRACE_USAGE_REPORTING=off (also false, 0, no) in the environment — the switch every trace client honours, checked before Parpt's own setting
• DO_NOT_TRACK=1 (also true, yes) in the environment, per consoledonottrack.com

The key under usage-reporting.key in application.yaml is the write key issued to Parpt; it can only add usage events and is not secret.

Details on what trace collects and why: https://github.com/Stephenson-Software/trace#usage-reporting

Contributing

This project is in early development. Contributions, suggestions and issue reports are welcome!

• Open an issue
• Fork and submit a PR
• Join the discussion

License

This project is licensed under the Stephenson Software Non-Commercial License (Stephenson-NC).
© 2025 Daniel McCoy Stephenson. All rights reserved.

You may use, modify, and share this software for non-commercial purposes only.
Commercial use is prohibited without explicit written permission from the copyright holder.

Full license text: Stephenson-NC License
SPDX Identifier: Stephenson-NC

About Preponderous

Preponderous Software builds developer tools, simulations and creative systems that help people focus their energy where it counts most.

Visit us at: https://www.preponderous.org