Menu
Six-phase deep research workflow. Collect → digest → outline → fill → refine → review → publish. For diving into unfamiliar domains.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | learn |
| description | Six-phase deep research workflow. Collect → digest → outline → fill → refine → review → publish. For diving into unfamiliar domains. |
Structured research methodology. From zero to published understanding in six phases.
Gather raw material. Docs, articles, code, issues, papers. Cast a wide net. Don't filter yet.
Read and annotate. Extract key concepts, patterns, gotchas. Discard irrelevant material.
Structure the knowledge. What are the core concepts? How do they relate? Build a skeleton.
Write detailed notes under each outline heading. Connect ideas across sections.
Edit for clarity. Remove redundancy. Add missing context. Polish explanations.
Self-review for accuracy. Have someone else review. Publish (internal wiki, gist, blog).
For quick codebase questions, skip this workflow and just ask directly:
"How does logging work?" / "What does async move { ... } do on line 134?" / "What edge cases does CustomerOnboardingFlowImpl handle?"
These are questions you'd ask a senior engineer — Claude handles them directly without the full research workflow.
"Ask Claude questions you'd ask a senior engineer." / "Use Claude Code for learning and exploration."
Turn ambiguous requirements into structured spec documents. Surface assumptions → interview → spec → human review → execute in fresh session. Spec is a contract, not a suggestion.
Pre-merge review. Reviews the diff, auto-fixes safe issues, flags destructive commands, runs verification. Evidence before assertions.
Execute an implementation plan with verification at every step. Tests first, then code. Stop on failures — never stack problems.
Systematic debugging. Reproduce → isolate → root cause → fix → verify. Root cause confirmed before any fix is applied. Never treat symptoms.
Build frontend interfaces with a committed aesthetic direction. Screenshot-based self-verification loop. Not generic defaults.
Read-only codebase exploration. Maps structure, patterns, and boundaries before any code is written. Use subagents to isolate context.
