一键导入
knowledge-flywheel
Analyze captured knowledge for patterns — detect repeated decisions, suggest conventions, surface "you keep running into X" insights.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Analyze captured knowledge for patterns — detect repeated decisions, suggest conventions, surface "you keep running into X" insights.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Behavioral rules that make AI coding agents more reliable — verification, self-correction, and scope discipline.
Debugging guidance and structured report template for thorough bug investigation, evidence gathering, and root cause documentation.
Cold-audit a completed delivery — verify the spec was actually delivered, challenge performative claims, and produce a what-landed report.
Guidelines for generating self-contained HTML mockups that look professional and are easy to iterate on.
Shared implementation guidance for making minimal, correct, maintainable code changes that fit existing systems.
The doctrine for `/roadmap-review` — interactive triage of roadmap-shape drift, walked one item at a time, with paste-ready resolution phrasing for the active sizing lens.
| name | knowledge-flywheel |
| description | Analyze captured knowledge for patterns — detect repeated decisions, suggest conventions, surface "you keep running into X" insights. |
| compatibility | opencode |
| metadata | {"audience":"any-agent","purpose":"knowledge-amplification"} |
Analyze the knowledge base (.hero/knowledge/) for patterns that should
be promoted to conventions, decisions, or warnings. This turns raw captured
notes into structured team intelligence.
/prime detects a growing knowledge base (>10 entries).hero/knowledge/notes//convention to codify a repeated practiceKnowledge flywheel — N entries analyzed
Patterns detected:
1. Convention candidate: "Error handling in API routes"
Seen in: 3 notes (auth-debugging, payment-retry, export-errors)
Suggestion: /convention codify API error response retry pattern
2. Recurring issue: "Database connection pool exhaustion"
Seen in: 2 notes (monday-outage, load-test-findings)
Suggestion: Add connection pool monitoring to operational runbook
3. No new patterns (N entries too unique to cluster)