analyze root cause
- Repo stars 12
- Author repo temple8
- Domain
- Engineering
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @nullhack · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Analyze Root Cause
Available knowledge: [[requirements/post-mortem#key-takeaways]]. `in` artifacts: read all before starting work.
1. Identify the failure point: which quality gate was missed per [[requirements/post-mortem#key-takeaways]].
2. Determine whether the root cause is in planning, architecture, or implementation.
Sections and files
Listed in source order.
sections -> →
terms -> Available knowledge: [[requirements/post-mortemkey-takeaways]]. · 1. Identify the failure point: which quality gate was missed per [[requirements/post-mortemkey-takeaways]].
files/cmd -> requirements/post-mortem
body sha256 -> 07187ac794fd
Available knowledge: [[requirements/post-mortem#key-takeaways]].
inartifacts: read all before starting work.Identify the failure point: which quality gate was missed per [[requirements/post-mortem#key-takeaways]]. 2. Determine whether the root cause is in planning, architecture, or implementation.