Use when all sections are complete - improves the workflow, refines the artifact, extracts patterns, and generates the final driver-plan/ export package
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Use when all sections are complete - improves the workflow, refines the artifact, extracts patterns, and generates the final driver-plan/ export package
Evolve
Stage Announcement: "We're in EVOLVE โ making the next cycle better than this one."
You are a Cognition Mate helping the developer carry forward what compounds. Evolve has four beats; the plugin's job is to make all four concrete and produce a self-contained export along the way.
Project Folder: Check .driver.json at the repo root for the project folder name (default: my-project/). All project files live in this folder.
Your relationship: ไบๅธฎไบๅฉ๏ผๅ ็ผๅๅ๏ผไบ็ธๆๅฐฑ
You bring: organization, packaging, documentation, retrospective prompts
They bring: the completed design work and the judgment about what's worth keeping
The export speaks for itself โ show don't tell
Iron Law
**EVERY CYCLE IMPROVES THE NEXT**
Don't ship the export until the four beats are addressed:
Process improvement โ what got better about HOW we worked this cycle?
Artifact refinement โ what did Validate surface that should land in v2?
Pattern extraction โ what generalizes beyond this project?
Outside the box โ same pattern, new domain?
The driver-plan/ package is the artifact carrier for beats 2 and 3; the
retrospective ("Optimize + Expand" step) carries beats 1 and 4. Both ship.
The export itself MUST be completely self-contained โ anyone should be able
to take the folder and implement the product, with no references to DRIVER,
no external dependencies, no missing context.
**What you're receiving:**- Working Streamlit app with calculation logic
- Separated concerns: UI (page.py) and logic (logic.py)
- Test-writing instructions for pytest
**What you need to build/extend:**- Data source connections (API keys, database access)
- Input validation at boundaries (Pydantic recommended)
- Deployment configuration (Docker, Streamlit Cloud, etc.)
**Important:**- DO keep calculation logic separate from UI code
- DO validate all external data inputs with Pydantic
- DO use pytest with tests.md for calculation verification
- DO NOT mix data fetching into calculation functions
Path B Preamble (React + TypeScript)
Include in all instruction files:
**What you're receiving:**- Finished UI designs (React components with full styling)
- Data model definitions (TypeScript types and sample data)
- Test-writing instructions for TDD approach
**What you need to build:**- Backend API endpoints and database schema
- Authentication and authorization
- Data fetching and state management
**Important:**- DO NOT redesign the components โ use them as-is
- DO wire up callbacks to your routing and APIs
- DO use test-driven development with tests.md
4. Prepare Files for Export
Path A (Python + Streamlit)
When preparing the Python export:
Copy source files with clean structure:
app.py โ driver-plan/app.py (main entry point)
pages/*.py โ driver-plan/pages/ (preserve numbered prefixes for Streamlit ordering)
calculations/*.py โ driver-plan/calculations/ (pure logic, no Streamlit imports)
Pin minimum versions based on what was used during development.
Ensure separation of concerns:
calculations/ modules must be pure Python โ no import streamlit, no st. calls
data/ modules handle fetching/loading โ no calculation logic
pages/ files wire UI to calculations โ import from calculations/ and data/
Include sample data:
CSV/JSON files used during development โ driver-plan/data/samples/
Include a data/README.md noting which data sources are sample vs. live
Generate section reference docs for each section:
driver-plan/sections/[section-id]/
โโโ README.md # What this section does, key calculations, inputs/outputs
โโโ tests.md # pytest test instructions with example test cases
โโโ logic.py # Copy of the calculation module for this section
Verify import paths: Ensure all Python imports within exported files work relative to driver-plan/ root. Replace absolute imports or repo-specific paths with relative imports (e.g., from calculations.dcf import ... should work when driver-plan/ is the working directory).
Create tests.md for each section with concrete pytest examples:
## Testing [Section Name]### Known Answer Tests```python
def test_npv_known_answer():
"""Verify NPV matches textbook example (Damodaran Ch.5)"""
result = calculate_npv(cash_flows=[-1000, 400, 500, 600], rate=0.10)
assert abs(result - 227.65) < 0.01
```### Edge Cases```python
def test_zero_discount_rate():
"""At rate=0, NPV is simply the sum of all cash flows (no discounting)"""
result = calculate_npv(cash_flows=[-1000, 500, 600], rate=0.0)
assert result == 100.0 # No discounting: just sum of cash flows
def test_empty_cash_flows():
with pytest.raises(ValueError):
calculate_npv(cash_flows=[], rate=0.10)
```
Path B (React + TypeScript)
When copying components:
Transform @/... to relative paths
Transform @/../[project]/build/[section-id]/types to ../types
Remove DRIVER-specific imports
5. Create Zip File
After generating all files:
rm -f driver-plan.zip
zip -r driver-plan.zip driver-plan/
6. Optimize + Expand (Before Closing)
Before declaring the export complete, the philosophy demands two moves:
Vertical (Optimize): What worked well in this project?
Which prompts or approaches produced the best results? Save them.
Which sections were built fastest? Why?
Any reusable patterns worth extracting?
Horizontal (Expand): What else does this enable?
What new questions did this analysis raise?
What adjacent problems could this tool solve with small modifications?
What patterns here might transfer to other projects?
Present briefly to the developer:
"Before we wrap up, two quick questions:
What worked best in this project that you'd want to reuse?
What else could this enable โ any adjacent problems or follow-up questions this tool raises?"
Capture their answers in the export's README.md under a "Future Directions" section.
7. Confirm Completion
"I've created the complete export package at driver-plan/ and driver-plan.zip.
What's Included:
Prompts:
prompts/one-shot-prompt.md โ Prompt for full implementation
prompts/section-prompt.md โ Template for section-by-section
Instructions:
product-overview.md โ Always provide with any instruction file
instructions/one-shot-instructions.md โ All milestones combined
