spark-prairie-fire

Sparks Start a Prairie Fire

"Though it is now only a tiny force, its development will be very rapid." — "A Single Spark Can Start a Prairie Fire"

Small does not mean hopeless; the key is to build a base area, not to be a roving bandit.

Use / Do not use

Use:

• Starting a new project, new field, or new capability from zero
• Resources are extremely limited, and the grand goal looks impossible
• Doing many scattered things but without accumulation
• Need to validate an idea with minimum investment

Do not use:

• Already has a solid foundation and is in the expansion stage
• The user has already clarified the entry point and only needs to execute
• Modifying an existing system: the existing code is the base area

Operating Procedure

1. Assess objective conditions: Does the need truly exist (is there dry kindling)? Does the environment allow development? Is the direction correct? Is there even a very small foundation to rely on? If conditions are insufficient → first investigation-first or adjust the direction, and do not rush to act.
2. Choose a base area: a specific entry point that satisfies four elements: core functionality is reliable, reusable, has a clear expansion path, and is proven solid. Choose where you have the greatest advantage and can gain the firmest foothold.
3. Take root: go deep at this point and produce reusable infrastructure and understanding.
4. Roving-banditism check(must pass before every expansion):
   • Has the previous entry point been proven solid?
   • Is this expansion a natural extension from the base area, not a leap?
   • Is the new content reusable, not one-off?
5. Three-step roadmap: plan only three steps, each with a success marker; proceed to the next step only after the previous one is solid.

Output Template

条件评估：需求真实 [是 / 否 / 不确定]，依据 ……；可依托基础 ……；主要障碍 ……
结论：具备发展条件 / 条件不足，需先 ……

根据地：……
- 我在这里的优势：……
- 能站稳的证据：……
- 向外扩展的路径：……

路线图：
第 1 步：…… → 成功标志：……
第 2 步：…… → 成功标志：……（第 1 步稳固后）
第 3 步：…… → 成功标志：……（第 2 步稳固后）

Discipline

• Do not expand before the base area is stable; do not constantly change direction and dabble superficially.
• Oppose both pessimism ("this little resource can't do anything") and recklessness ("let's just start and attack everywhere").

Handoff

• Concentrate forces on the base area → concentrate-forces
• Validation of each expansion step → practice-cognition
• Incorporate into a long-term phase framework → protracted-strategy

Original basis:original-texts.md