Дата: 2026-03-30 Автор: Coordinator (AI) Статус: 🟡 TS — Ожидает апрува Parent HL: HL-TFW-11 Research: RES__TFW-11
Интегрировать RESEARCH в plan.md (гейт после HL) и устранить все pipeline desyncs из Phase A REVIEW (Tech Debt #1-8) + review findings.
.tfw/README.md, init.md, root README.md.claude/commands/tfw-research.md — Phase C| Файл | Действие | Описание |
|---|---|---|
.tfw/workflows/plan.md |
MODIFY | RESEARCH gate after Phase 3, pipeline diagram update |
.tfw/README.md |
MODIFY | Pipeline diagram (§Task Lifecycle), artifact types table (add RES) |
.tfw/init.md |
MODIFY | Pipeline status line in Step 4 code block |
README.md (root) |
MODIFY | Key Concepts pipeline string |
.tfw/conventions.md |
MODIFY | §2: add RES.md + research.md to Required Artifacts. §8: “three” → “four” |
.tfw/glossary.md |
MODIFY | Workflow def: “Three” → “Four”. Coordinator role: add RES. Task Naming: add RES__ example. Add “Read-only AG” term |
Бюджет: 0 новых файлов, 6 модификаций. ≤7 файлов ✅, ≤4 новых ✅, ≤6 modified ✅
Insert new Phase 3.5 between current Phase 3 (Review & Refine) and Phase 4 (Decide Scope):
## Phase 3.5: RESEARCH Gate
After HL is approved, the coordinator:
1. **Assess** — give a recommendation: is RESEARCH needed? (with rationale)
- Complex/ambiguous tasks → recommend RESEARCH
- Simple/clear tasks → recommend skip
2. **Ask** — present recommendation to user, ask for confirmation
3. **Never skip silently** — even if recommending skip, wait for user response
If RESEARCH is needed:
- Run the research workflow (`.tfw/workflows/research.md`) inline
- RES file is created in the task folder
- After RESEARCH completes → proceed to Phase 4
If RESEARCH is skipped:
- User confirms skip → proceed directly to Phase 4
Also update the pipeline diagram in plan.md Status Transitions section to include 🔬 RES.
.tfw/README.md — pipeline + artifact table⬜ TODO → 🔵 HL → 🔬 RES → 🟡 TS → 🟠 ONB → (develop) → 🟢 RF → 🔍 REV → ✅ DONE
Add note: “RES is optional — user can skip from HL directly to TS”
| **RES** | Research Report | Structured investigation: decisions, questions, stage logs |
.tfw/init.md — pipeline status lineUpdate the status line in Step 4 code block:
> Statuses: ⬜ TODO → 🔵 HL → 🔬 RES → 🟡 TS → 🟠 ONB → 🟢 RF → 🔍 REV → ✅ DONE | ❌ BLOCKED
README.md (root) — Key ConceptsUpdate the pipeline string in Key Concepts section:
- **Task lifecycle**: `⬜ TODO → 🔵 HL → 🔬 RES → 🟡 TS → 🟠 ONB → 🟢 RF → 🔍 REV → ✅ DONE` (RES optional)
.tfw/conventions.md — text fixes.tfw/templates/RES.md — canonical Research Report template..tfw/workflows/research.md — canonical research workflow.
```.tfw/glossary.md — text fixesWorkflow definition (line ~73): “Three canonical workflows” → “Four canonical workflows: plan (HL→RES→TS), research (structured investigation), handoff (ONB→execute→RF→REVIEW), resume (status matrix→next phase)”
Coordinator role (line ~89-94): add “- Writes RES (research mode)” or “- Conducts RESEARCH and writes RES files”
Task Naming section (line ~41): add RES__{PREFIX}-{N}__*.md to the file examples
Add new term — Read-only AG: “A mode within RESEARCH where the agent autonomously reads project files and web sources but writes only to the RES artifact. No code changes, no other file modifications. Formally CL with expanded read permissions.”
.tfw/README.md, init.md, root README.md (all show 🔬 RES).tfw/README.md artifact types table includes RES.tfw/ returns 0 matches| Риск | Mitigation |
|---|---|
| plan.md restructuring breaks existing flow | Preserve all existing phases, only insert 3.5 between 3 and 4 |
| Missing pipeline instances | Final grep: TODO.*HL.*TS across all .md to catch stragglers |
| *TS — TFW-11 / Phase B: Integration — Plan Gate + Pipeline Desyncs | 2026-03-30* |