compounder

Combine weekly outputs from all skills into a contextual feedback loop.

3|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/vxcozy/architect-system --skill compounder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compounder
Source: https://github.com/vxcozy/architect-system/tree/main/.claude/skills/compounder
Command: npx skills add https://github.com/vxcozy/architect-system --skill compounder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly reviews are fragmented and fail to compound gains over time; this skill synthesizes disparate outputs into a cohesive, actionable feedback loop that improves ongoing performance across the audit-architect-analyst-refinery-compounder cycle.

Core Features & Use Cases

  • Synthesize state and artifacts (system/state.md, audit reports, blueprints, and weekly reviews) into a single progress narrative.
  • Output a weekly report to system/compounder/week-{date}.md and feed insights back to the audit.
  • Identify friction, track patterns, and update the system map to guide next week's planning.

Quick Start

Run the compounder at the end of the week to generate system/compounder/week-{date}.md and push insights back to the audit.

Frequently Asked Questions about compounder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate my weekly review to compound productivity gains?

A weekly review feedback loop combines current state files, audit reports, and blueprints into a single progress narrative. This contextual mechanism surfaces friction and recurring patterns to guide next week's planning and improve ongoing performance.

How do I generate a weekly review report from multiple audit outputs?

Generate a cohesive weekly report by reading system state, audit reports, blueprints, and prior reviews. The process synthesizes these artifacts into a single narrative saved to system/compounder/week-{date}.md while pushing insights back to the audit.

Can I use pattern recognition to identify friction across my workflow?

Yes, pattern recognition identifies workflow friction by analyzing system state, audit reports, and prior reviews. The mechanism surfaces recurring bottlenecks and updates the system map to guide next week's planning and prevent similar friction.

Does the weekly review process require prior audit reports and blueprints?

Yes, the weekly review process reads prior audit reports, blueprints, system state, and previous weekly reviews. These artifacts provide the necessary context to synthesize a cohesive progress narrative and establish an actionable feedback loop.

What is the best way to track productivity patterns across end-of-week reviews?

The best way to track productivity patterns is using a compounding feedback loop that continuously updates the system map. It synthesizes weekly outputs into a single report, ensuring identified patterns guide future audit cycles and planning.