Project Cockpit

Keep the current phase, situation, blocker and next step visible so interrupted project work can restart without rebuilding context.

Who this is for

For individual PMs and creators managing several active projects whose work is frequently interrupted.

Result

A local re-entry point for every project, plus lightweight todos, a resolved archive and JSON backup.

Start here

  1. Download the fixed v1.0.0 package and open index.html or start the local server.
  2. Create one project and select its current phase.
  3. Record the situation, problem and next executable action.
  4. Keep small daily actions in the separate todo view.
  5. Export JSON before clearing browser data or changing browser profiles.

Restart the project without reconstructing the whole story

A task name may survive an interruption while its reasoning disappears. Project Cockpit keeps phase, situation, blocker and next step together so each project has one visible re-entry point.

Start with one active project

Replace a synthetic example with one real project, choose its phase and record the shortest note that explains the current situation, problem and next action.

What the current validation establishes

Automated checks cover package structure, JavaScript syntax, private-source terms and unexpected network APIs. Clean-browser checks confirmed synthetic demo loading, phase-note persistence after reload and narrow-screen operation. Independent adoption is not claimed.

Local data is the main benefit and the main limitation

No project data is sent to a backend, but browser site data can be cleared. JSON export is a manual recovery path, not cloud backup or encrypted storage.

Download the fixed v1.0.0 release

The public repository and versioned ZIP are available under the MIT License. A SHA-256 checksum is included with the release assets.

Limits

Data stays in the current browser. The tool has no account, backend, cloud sync, encrypted storage or team collaboration. Clearing site data can remove the records.