forewrite

Write present and future pages to compare project idea gaps.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/songlairui/agent-monad --skill forewrite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forewrite
Source: https://github.com/songlairui/agent-monad/tree/main/skills/forwrite
Command: npx skills add https://github.com/songlairui/agent-monad --skill forewrite

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

这个 Skill 帮你在真正启动一个项目之前,先判断它是不是值得启动,避免把兴致、白日梦和真实需求混在一起。

Core Features & Use Cases

  • 双页同书:同时写出当下页和未来页,分别记录现在为什么想做、未来会看到什么。
  • 交叉阅读:把两页摊开比对,判断差距属于已到达、最小动作、真项目、放弃,还是更大梦的一部分。
  • 项目级决策:适合新工具、新流程、新系统、基础设施改造等容易一时冲动就开工的场景。
  • 执行分流:根据 verdict 决定是直接做最小动作、进入更正式的锚定流程,还是干脆不启动。

Quick Start

请用 forewrite skill 先帮我写当下页和未来页,再交叉阅读并给出一个 verdict。

Frequently Asked Questions about forewrite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide if a project impulse is worth executing?

To decide if a project impulse is worth executing, use a two-page decision ritual that compares your current state against concrete future scenes to output a structured verdict like real_project or abandon.

What is the best way to evaluate new system and workflow ideas before starting?

Evaluating new system and workflow ideas requires cross-reading a present page and a future page to categorize the gap into actions like minimum_action, real_project, or outer_dream.

How can I structure project decision making for ambiguous infrastructure ideas?

Structure project decision making for ambiguous infrastructure ideas by performing a two-page decision ritual that captures intended uses and current state to produce an execution verdict.

When should I use a formal project verdict instead of just taking minimum action?

You should use a formal project verdict instead of minimum action when cross-reading your present and future pages reveals a significant gap that qualifies the idea as a real_project requiring formal anchoring.

Does this project evaluation method work for new tools or only large infrastructure changes?

This project evaluation method works for both new tools and large infrastructure changes, specifically targeting moments when excitement needs a structured pause before committing to an execution path.