Release: Issues+Systems, milestone-as-plan, plugin reliability/skills/dedup, compaction hygiene #71
@@ -77,6 +77,9 @@ Keep task state honest — this is what makes the project a trustworthy record:
|
||||
that changes direction — write a short dated note on the project (create_note)
|
||||
capturing what happened (the pivots, not just the wins), and set the finished
|
||||
task to done.
|
||||
- When you record a problem you solved, capture symptom → root cause → fix
|
||||
(tag it `issue`) so it's findable later — even one solved in passing is worth
|
||||
two lines, so it isn't diagnosed from scratch next time.
|
||||
|
||||
Scribe maintains a Rulebook system (Rulebook -> Topic -> Rule). Rules carry
|
||||
an actionable statement plus optional Why and How-to-apply context. At the
|
||||
|
||||
Reference in New Issue
Block a user