메뉴
Identify patterns across products — what's working that should propagate, what's failing in similar ways, what knowledge should become MEMORY.md entries.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | cross-product-learner |
| description | Identify patterns across products — what's working that should propagate, what's failing in similar ways, what knowledge should become MEMORY.md entries. |
| model_tier | opus |
Saved to brain/decision-log/learnings-YYYY-MM-DD.md and updates to MEMORY.md:
## Cross-Product Learnings — <week of>
### Patterns that should propagate
1. **<pattern>** — first seen in <product>, observed again in <product>. Action: extract to <skill / template / knowledge-base file>.
2. ...
### Patterns that are failing repeatedly
1. **<anti-pattern>** — observed in <products>. Reason it keeps happening: <root cause>. Mitigation: <change>.
### New entries proposed for MEMORY.md
- [<title>](<file>) — <one-line hook>
### New entries proposed for factory/playbooks/
- factory/playbooks/<stage>/<filename>.md — covering <topic>
### Templates that need updating
- templates/<file> — change: <what>
### Skills that need updating
- skills/<name>/SKILL.md — change: <what>
decisions/ entries from the past week.decisions/ foldersbrain/decision-log/MEMORY.mdSlice a goal into the smallest feature slices that can each be PROVEN — every slice ships with a named eval and an end-to-end test, and a slice you can't evaluate or test doesn't get selected. Use after the goal is set and before the spec, so only provable features make the build.
Guided, stateful provisioning of a product's production stack — deep-links, key-format validation, a secrets backend (fnox recommended, or user-touched .env.local), a resumable ledger, CLI automation after signup, and a blocking A1–A10 live gate. Hands off to /security-check → /ship. The walked version of SETUP.md.
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
Launch the factory's control plane — scaffold and fill FACTORY-ORDERS (weekly mandate + hard budget), STANDING-ORDERS (autonomous-program authority), HEARTBEAT (weekly pulse), and write lifecycle gates for every registered product. A deliberate one-time ritual (re-run to audit); invoke as /factory-launch, not auto-triggered.
One-shot a new product — folders, Next.js starter, product.config.json, CLAUDE.md, scope.md, PRD skeleton, SETUP.md checklist. The Lovable-like ignition.
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.