Textum

🕸️ Textum

Weave your ideas into runnable code

A workflow that helps AI make fewer mistakes Not by making AI smarter, but by making the process more controllable

 English | 中文

⚠️ Note: The old commands version is deprecated and no longer supported. Only the skill version is currently supported.

🤔 What's this all about?

Ever run into these problems?

• 💬 You spend ages explaining requirements to AI, only for it to forget what you said halfway through
• 🔄 One tiny requirement change and suddenly you're rewriting everything
• 🎲 Every generation is a roll of the dice — quality is pure luck

That's exactly what Textum is here to fix.

It won't make AI any smarter, but through structured workflow and validation, it helps AI avoid the kind of mistakes that shouldn't happen in the first place.

---

✨ How does it work?

Just describe your idea in plain language. Textum breaks the whole thing down into 4 phases:

Step 1: 📝 Requirements Clarification (PRD)

"So, what are we building?"

AI chats with you to turn fuzzy ideas into a clear requirements doc. Every feature gets a number (like FEATURE-001) — no more repeating yourself later.

Step 2: 🏗️ Technical Decisions (Scaffold)

"What's the tech stack? How do we structure this?"

Lock down the architecture, pick your technologies, define the modules. This creates a "global context" that keeps all the coding consistent.

Step 3: 🧩 Task Breakdown (Split)

"What's the game plan?"

Break requirements into bite-sized tasks (Stories) — think sticky notes. One Story, one job. Finish it, then move on.

Step 4: 💻 Code Implementation (Story)

"Let's write some code!"

AI tackles one Story at a time, laser-focused without distractions. Each Story gets validated when done — no drifting off course.

⚠️ Experimental: Story Full Exec supports batch execution of multiple Stories (sequential, no rollback). This feature is experimental — use at your own discretion. ⚠️

---

🎯 Why all these steps?

Picture this: you hand AI a 10-page requirements doc and say "build it all." What happens?

By feature #5, AI has already forgotten what fields were in feature #1. 😅

It's not that AI is dumb — it just has limited "memory." The more info you throw at it, the easier it loses track.

That's why Textum's philosophy is simple: Less is more

The Old Way	The Textum Way
Dump all requirements on AI at once	📦 Feed it phase by phase, only what's needed now
Keep saying "you know, that login API thing"	🔗 Just say API-001 — short and unambiguous
One requirement change = regenerate everything	🎯 Only regenerate what's actually affected

---

📏 What kind of projects work best?

Project Size	Feature Count	What to Expect	Examples
🌱 Small	10-15	✅ Solid results	Expense tracker, todo app, personal notes
🌿 Medium	15-25	✅ Solid results	Simple blog, survey system
🌳 Larger	25-35	⚠️ Needs human review	Multi-role admin panel, booking platform

💡 Even bigger? Split it into independent sub-projects and run each through Textum separately.

Simulation Test Reports