Jonah Schulte
|
7feab0e233
|
docs: update all documentation for super-dev-pipeline
Updated documentation to accurately reflect current state:
KEY CHANGES:
1. super-dev-pipeline is now the production workflow (not story-pipeline)
2. Corrected token estimates (40-60K vs 65% claim for story-pipeline)
3. Updated autonomous-epic v2.0 description
4. Clarified workflow purposes and use cases
DOCUMENTATION UPDATED:
- INTEGRATION-NOTES.md
* Updated to focus on super-dev-pipeline as production solution
* Explained evolution: story-pipeline → brownfield problem → super-dev-pipeline
* Workflow comparison table shows all three options
* Task-based completion explained
* Anti-vibe-coding enforcement detailed
- PR-STORY-PIPELINE.md
* Renamed focus to super-dev-pipeline (the actual deliverable)
* Updated all metrics to 50% savings (not 65%)
* Added problem statement about brownfield
* Explained adaptive implementation
- autonomous-epic/README.md
* Updated to reference super-dev-pipeline
* Corrected token estimates (40-60K per story)
* Updated time estimates (2-5 hrs small, 5-10 hrs medium, 10-20 hrs large)
* Example session shows super-dev-pipeline steps
KEY POINTS CLARIFIED:
- super-dev-pipeline: Production (greenfield + brownfield, 40-60K tokens)
- story-pipeline: Greenfield only (25-30K tokens, 65% savings)
- super-dev-story: Legacy (100-150K tokens, allows vibe coding)
- autonomous-epic v2.0 uses super-dev-pipeline by default
- Task-based completion (not status-based)
- Anti-vibe-coding enforcement via step-file architecture
- Works for real-world scenarios (most work is brownfield!)
All documentation now consistent and accurate.
|
2025-12-28 12:23:55 -05:00 |