964 B
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| feedback_ct_thoughts_backlog | Where ClaudeTools harness ideas go (CT_THOUGHTS.md) and the trigger phrase to append one |
|
ClaudeTools harness ideas (the internal tooling itself, not client work) go in
docs/CT_THOUGHTS.md — the CT analogue of feedback_rmm_thoughts_backlog's
RMM_THOUGHTS.md. Pipeline: thought (Status: Raw) -> discuss -> spec (/shape-spec or a
concept doc) -> roadmap -> build.
Why: keeps ClaudeTools-self ideas in one durable backlog instead of evaporating into
session logs; parallels the GuruRMM thought pipeline.
How to apply: when Mike/Howard say "ct thought: " / "add to ct thoughts" / "park
this as a ct thought", append it to docs/CT_THOUGHTS.md with who/when + a Status. Don't
build until an explicit go (per feedback_stream_of_thought_design). First entry =
ClaudeTools 3.0 web co-work vision (see project_ai_auth_product_boundary for its auth model).