القائمة
Use after completed Pulse work when the user asks to capture post-cycle machine-readable learnings for future planning and execution.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | compounding |
| description | Use after completed Pulse work when the user asks to capture post-cycle machine-readable learnings for future planning and execution. |
| metadata | {"version":"1.4","ecosystem":"pulse","position":"8 of 9 — runs after reviewing, before next feature","dependencies":[{"id":"beads-cli","kind":"command","command":"br","missing_effect":"unavailable","reason":"Compounding reads bead history to reconstruct executed work."}]} |
If preflight readiness is missing, stale, or blocked (check .pulse/tooling-status.json), stop and invoke pulse:using-pulse before continuing.
Compounding turns completed feature work into reusable memory for future planning and execution.
Compounding is the canonical post-cycle, machine-readable learning pass for completed Pulse work. Use pulse:dream for runtime-artifact consolidation outside that post-cycle moment.
pulse:reviewing completes and feature is mergedSkip only when no durable/reusable learning emerged.
All operational rules live in references/runtime-appendix.md. Treat that file as canonical for:
applicable-when must be specific)critical-patterns.md.pulse/memory/*.pulse/memory/learnings/YYYYMMDD-<slug>.md..pulse/STATE.md and .pulse/state.json.references/runtime-appendix.md — canonical runtime contractreferences/learnings-template.md — learnings file structurereferences/analysis-prompts.md — prompts for pattern/decision/failure analysisreferences/corrections-and-ratchets.md — correction and ratchet file structuresUse when the user asks to distill accumulated dev-notes into reader-facing topic knowledge, rather than to capture a new note or update machine memory.
Use when implementing approved Pulse beads, either as a swarm worker or as a single worker when swarming is unavailable.
Use before implementation planning when feature intent is clear but implementation decisions are still unresolved, and the user needs those decisions locked first.
Use after pulse:exploring when locked decisions are ready and the user needs a mode-gated plan with an approved work shape and current-work prep for validation.
Use when starting any Pulse workflow, resuming a Pulse session, or before planning or execution when tool readiness or onboarding state may block the flow.
Use after execution completes when the user needs final quality verification and release-readiness review before closeout.