메뉴
Reflect on external content (LinkedIn posts, articles, repos) — analyze, cross-reference with Demerzel ecosystem, extract lessons, compound learnings.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when a pull request needs review by a different AI model than the one that authored it, or when configuring cross-model code review pipelines in CI/CD.
Run Demerzel's autonomous driver — full cycle or individual phases across all repos
Capture meaningful session state (current cursor, in-flight work, live hypotheses, open questions, do-NOT-carry-forward, success criteria) to state/digests/latest.md so the next session — including one after auto-compaction — can re-enter without re-discovering context cold. Distinct from /learnings (which captures surprises). Validates against docs/contracts/digest-schema.json.
Autonomous research scheduler — selects the most under-researched department by coverage ratio, generates questions from completeness gaps, cross-model validates, auto-produces courses at T>=0.8, rate-limited to 6 cycles/day with kill switch
Personalized AI tutor — turns any topic into a customized, progress-tracked learning course. Use when the user wants to LEARN a concept, skill, language, tool, or domain. Creates a MISSION, curated RESOURCES, iterative lessons with self-checks, and learning-records that persist across sessions. NOT for interrogating the user about their own design (use brainstorming/IDSD for that).
Run one bounded supervised autonomous cycle on the Demerzel governance repo. Picks the smallest unchecked governance slice inside allow_edit, implements it, runs the oracle (`pwsh scripts/verify.ps1`), emits cycle evidence, and stops. Refuses to run unless dev-process-overseer reports loop-eligible and the preflight passes. Use when asked to "run one supervised loop", "advance governance autonomously", or "do one cycle and stop".
| name | demerzel-reflect |
| description | Reflect on external content (LinkedIn posts, articles, repos) — analyze, cross-reference with Demerzel ecosystem, extract lessons, compound learnings. |
Analyze external content and extract actionable lessons for the GuitarAlchemist ecosystem.
/demerzel reflect <url> — analyze a single piece of content
/demerzel reflect --batch <file> — analyze multiple URLs from a file
/demerzel reflect --topic "claude code" — search and analyze trending content
For each claim or technique in the content, check against our ecosystem:
| Question | How to Check |
|---|---|
| Do we already do this? | Search skills, policies, grammars |
| Do we do it better? | Compare with evidence from our experience |
| Should we adopt this? | ERGOL check — does it have a real consumer? |
| Can we contribute back? | Do we have insights the author lacks? |
## Reflection on: [Title] by [Author]
### We Agree (with citation)
- [Specific point] — maps to our [artifact/principle]
### We Should Steal
- [Specific technique] — consumer: [who benefits], timeline: [when]
### We Could Teach
- [What we know that they don't] — evidence: [our experience]
### We Challenge
- [Claim we'd push back on] — our evidence: [data/experience]
### BS Score
- Specificity: PASS/FAIL
- Falsifiability: PASS/FAIL
- Density: PASS/FAIL
- Commitment: PASS/FAIL
- Verdict: T/U/C
/demerzel reflect https://charliehills.substack.com/p/claude-code-beginner-advanced
→ Reflection: 48-skill library, parallel agents, context management
→ We should steal: skill packaging as installable ZIPs
→ We could teach: constitutional governance, ERGOL/LOLLI, meta-tools
/demerzel reflect https://medium.com/@talirezun/from-lab-to-life
→ Reflection: 3-phase methodology, context engineering, hybrid debugging
→ We should steal: production deployment discipline, cost tracking
→ We could teach: governance hierarchy, tetravalent logic, D_c metrics