Phase 1 / Ep 06: The First Workflow of the Generation System

⏱ Est. reading time: 4 min Updated on 4/13/2026

You now have the legal constraints of GEMINI.md, the interception mechanism of using-superpowers, and have expanded the system's infinite memory with planning-with-files.

But if you were to tell the Agent now: "Create the user table and then build an API for it." Even if the Agent knows the rules, it would still lack a "sense of pacing" for its work—it might still dump three thousand lines of code with errors on you all at once.

In large, established internet companies, everything is done with a standard Development Pipeline (SOP). In the hands of an Agent, this is called a Workflow.

1. Workflow File .agents/workflows/feature-development.md

We are preparing to establish the first standardized process checklist in the project. Store it in the project's workflow directory. This file is truly a script that "guides behavioral execution power."

description: T-Block Core New Feature Development Standardization Process

# Feature Development Workflow (SOP)

When you receive a complex user requirement instruction, refrain from immediately writing business code. Please strictly follow this SOP in sequential order:
// turbo-all

1. **Intent Acquisition and Realization:**
   Read the requirement itself and clarify the objective in mind. Immediately invoke and review `docs/task_plan.md`. If it does not meet the existing architectural structure, immediately initiate discussion to modify the Plan.

2. **Behavioral Anti-Corruption:**
   If there is any uncertainty about the original project architecture, prioritize initiating a search (`grep`). Do not arbitrarily invent file paths.

3. **Test-Driven Development (TDD):**
   As soon as it is confirmed that code functionality needs to be modified/added, you **must** first proceed to modify the corresponding `.test.ts` / `.spec.ts` unit tests and run them once! The test will inevitably throw red errors (failures).

4. **Feature Iteration:**
   With the primary goal of passing the aforementioned red-text tests, iteratively add business code. Continue until the terminal displays a green `Test Passed`.

5. **Summary and Archiving:**
   Write down any difficulties encountered or valuable design concepts in `docs/findings.md`, and then update your checked subtasks for today in `task_plan.md`.

2. What is the Black Magic of the "// turbo-all" Marker?

Take a close look at the // turbo-all comment in the workflow! This is profoundly meaningful in advanced Agent systems. Through this declarative annotation, it directly authorizes the underlying Agent: "Under this standard process step, if there is a need to run safe exploratory terminal commands or non-destructive directory viewing, feel free to operate, automatically accelerate, and make autonomous judgments, without requiring human intervention and approval at every step."

This constitutes the initial state machine of a fully self-governing state.

3. Mission Accomplished: Phase 1 Acceptance

Congratulations! At this point, our "foundation" is 100% solidly laid. To summarize what currently exists in the T-Block project:

  • A concise [One-Pager Intent] (representing human will)
  • [GEMINI.md] (stipulating overall baselines and modes of conduct)
  • .agents/skills/using-superpowers/ (the guardian against hallucinations)
  • .agents/skills/planning-with-files/ (the hard drive recording method to prevent cognitive damage)
  • .agents/workflows/feature-development.md (Standard Pipeline Onboarding Guide)

The most perfect anti-interference cybernetic organism has been born.

Are you ready? In the upcoming Phase 2, we will press the ignition switch. We will throw humanity's One-Pager into this machine and experience firsthand what AI-led "rapid PRD fission" and "selection debate" truly mean.