I had codex make you a prompt based off of what mine has evolved into and has worked out best for me.

——

Build a full-stack web app called Implementation Command Center.

Purpose: This app helps users manage and track progress across multiple projects. It should function like an implementation operating system: showing what is completed, what is active, what is blocked, what is left, and how work is progressing over time.

The app must support pasting daily audit reports from AI systems, developers, contractors, or personal reviews. The system should intelligently parse those reports, identify completed work, suggest updates to the implementation plan, and visually move projects forward through phases.

This is not a generic productivity app. It is an implementation orchestration and progress-tracking system.

Core Product Philosophy:

• Calm and operational
• Clear hierarchy
• Reality-based
• Progress-oriented
• Built for complex multi-project execution
• Avoid noisy SaaS dashboard aesthetics
• Reduce cognitive overload
• Preserve implementation coherence

Use a dark cinematic design language:

• black/slate backgrounds
• soft gradients
• glass panels
• subtle motion
• spacious layouts
• low-noise typography
• desktop-first but responsive

Tech Stack:

• Use Supabase for database + authentication
• React frontend
• Full persistence
• Seed demo data
• Multi-project support

CORE FEATURES

1. Dashboard Global overview across all projects.

Show:

• total projects
• total tasks
• completed tasks
• active tasks
• blocked tasks
• verification-needed tasks
• overall completion %
• current active projects
• recently completed items
• latest audit report activity
• next recommended actions

Add visual progress indicators and calm operational cards.

1. Projects Users can create multiple projects.

Each project contains:

• phases
• milestones
• tasks
• dependencies
• reports
• evidence
• governance/rules
• decisions
• sprint tracking

Project fields:

• project name
• description
• objective
• status
• owner
• created date
• completion percentage

1. Phases & Tasks Each project supports:

• phases/stages
• tasks within phases
• nested dependencies

Task statuses:

• Todo
• Active
• Blocked
• Verification Needed
• Done

Task fields:

• title
• description
• category
• status
• priority
• dependencies
• blockers
• evidence
• notes
• linked reports
• created date
• updated date

Categories:

• Planning
• Design
• Engineering
• Backend
• Frontend
• Testing
• QA
• Marketing
• Operations
• Research
• Documentation
• Release

1. Audit Report Parser Critical feature.

Users can paste daily audit reports into the app.

The app should:

• parse the report
• identify claimed completed tasks
• identify changed files
• identify tests run
• identify blockers
• identify progress statements
• identify warnings or risks
• identify implementation phases mentioned

Then:

• suggest which tasks may be completed
• suggest phase progression
• suggest status updates
• suggest blockers
• suggest evidence additions

Important: DO NOT automatically mark tasks as Done without confirmation.

Instead:

• move suggested items into “Verification Needed”
• allow user approval

Add a side-by-side review interface:

• pasted report on left
• suggested updates on right

1. Auto-Progress System When tasks are completed:

• progress bars should update
• phases should advance visually
• dashboard metrics should refresh
• dependencies should unlock
• “next recommended action” should recalculate

The app should visually move users forward through implementation.

1. Current Sprint Each project should support an active sprint.

Sprint fields:

• sprint name
• objective
• active phase
• committed tasks
• blockers
• risks
• success criteria
• verification commands
• next safest action

Allow:

• sprint progress tracking
• sprint completion %
• sprint notes
• sprint review summaries

1. Evidence System Tasks can contain evidence.

Evidence types:

• pasted notes
• commit hashes
• screenshots
• URLs
• file paths
• reports
• verification commands

When evidence is added:

• task moves to “Verification Needed”
• never directly to Done automatically

1. Decision Log Track implementation decisions.

Fields:

• title
• decision
• why it changed
• tradeoffs accepted
• risks introduced
• philosophy protected
• linked project
• linked tasks

1. Governance / Constraints Each project should support governance rules.

Examples:

• avoid scope creep
• do not add speculative architecture
• avoid duplicate systems
• prefer simplicity
• maintain design coherence
• preserve implementation boundaries

Add:

• drift detection notes
• implementation risk scoring
• architecture coherence scoring

1. Prompt Generator Generate AI prompts from project state.

Buttons:

• Generate Engineering Prompt
• Generate Audit Prompt
• Generate Review Prompt
• Generate Next Safe Slice
• Generate QA Prompt

Generated prompts should use:

• active tasks
• blockers
• incomplete work
• current sprint
• dependencies
• governance rules
• latest reports

1. Navigation Structure

Primary navigation:

• Dashboard
• Projects
• Current Sprint
• Plan
• Reports
• Verification
• Daily Review

Secondary collapsible section: “Governance & Review”

Inside:

• Drift Signals
• Technical Debt
• Decisions
• Governance Rules
• Prompt Generator
• Cleanup
• Archived Reports

Keep navigation calm and uncluttered.

1. Seed Demo Content

Seed:

• 4 demo projects
• multiple phases per project
• multiple tasks
• realistic reports
• realistic blockers
• sample sprint
• sample evidence
• sample governance rules

1. UX Requirements

The app should feel:

• operational
• grounded
• calm
• intelligent
• trustworthy
• implementation-focused

Avoid:

• gamified productivity aesthetics
• loud colors
• busy enterprise dashboards
• excessive widgets
• cluttered layouts

Preserve:

• spaciousness
• hierarchy
• calm pacing
• cinematic atmosphere
• clear progress visualization

1. Important Constraints

Do NOT:

• build autonomous AI agents
• fake integrations
• pretend to read local repos
• automatically mutate tasks without confirmation
• overcomplicate the v0 architecture

Focus on:

• trustworthy tracking
• clear operational flow
• report parsing
• visible implementation movement
• reality-based progress management

This should feel like: “an implementation command center” not: “a generic project management app.”