Good idea, and the part comparing Railspike to built-in plan modes is the most convincing bit: plans as plain files in the repo that survive compaction and agent switches. I'd move it much higher, since "why not just use plan mode?" is the first thing most readers will ask.
What I'd fix:
- There's no link to the repo anywhere in the post. Put it in the first or second line.
- The quickstart is buried. "Copy RAILSPIKE.md in, then say 'Write Step 1 of RAILSPIKE.md'" is the hook, and it sits near the very end. Lead with it and tell the backstory after.
- Show one real plan-prompt. A short Step 1 or Step 3 file would do more than several paragraphs describing them.
- The steps change names. First they're brainstorming/outlining/planning/development, later ideation/high-level plan/development plan. Pick one set. Debug mode gets one mention and no explanation.
- "Not unlike agile or waterfall" compares it to two opposites. "A lightweight waterfall" says what you mean.
- A few sentences are hard to parse. "Our agentic developers and us" could mean agents or people. The parenthetical "Sometimes a one-shot fix really is" reads as cut off. "Web-based online social spaces frameworks" needs untangling.
- Say when it's overkill. Four steps cost time and tokens, and one sentence on when you skip it would make "almost completely eliminated" easier to believe.
- Small stuff: "promt" typo, "This is not all, we keep finding" needs a period or a dash, and "super easy… super quickly" repeats.
The core pitch (the agent writes its own prompt, you edit it before any code exists) is clear and useful. It just needs to show up sooner.