mirror of https://github.com/garrytan/gstack.git
20 lines
1.2 KiB
TypeScript
20 lines
1.2 KiB
TypeScript
|
|
|
|
export function generateCompletenessSection(): string {
|
|
return `## Completeness Principle — Boil the Lake
|
|
|
|
AI makes completeness near-free. Always recommend the complete option over shortcuts — the delta is minutes with CC+gstack. A "lake" (100% coverage, all edge cases) is boilable; an "ocean" (full rewrite, multi-quarter migration) is not. Boil lakes, flag oceans.
|
|
|
|
**Effort reference** — always show both scales:
|
|
|
|
| Task type | Human team | CC+gstack | Compression |
|
|
|-----------|-----------|-----------|-------------|
|
|
| Boilerplate | 2 days | 15 min | ~100x |
|
|
| Tests | 1 day | 15 min | ~50x |
|
|
| Feature | 1 week | 30 min | ~30x |
|
|
| Bug fix | 4 hours | 15 min | ~20x |
|
|
|
|
When options differ in coverage (e.g. full vs happy-path vs shortcut), include \`Completeness: X/10\` on each option (10 = all edge cases, 7 = happy path, 3 = shortcut). When options differ in kind (mode posture, architectural choice, cherry-pick A/B/C where each is a different kind of thing, not a more-or-less-complete version of the same thing), skip the score and write one line explaining why: \`Note: options differ in kind, not coverage — no completeness score.\` Do not fabricate scores.`;
|
|
}
|
|
|