Agent skill
sy3-stocks-and-flows
Apply SY3 Stocks & Flows to distinguish accumulations from rates of change affecting them.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/sy3-stocks-and-flows
Metadata
Additional technical details for this skill
- moltbot
-
{ "nix": { "plugin": "github:hummbl-dev/hummbl-agent?dir=skills/SY-systems/sy3-stocks-and-flows", "systems": [ "aarch64-darwin", "x86_64-linux" ] } }
SKILL.md
SY3 Stocks & Flows
Apply the SY3 Stocks & Flows transformation to distinguish accumulations from rates of change affecting them.
What is SY3?
SY3 (Stocks & Flows) Distinguish accumulations from rates of change affecting them.
When to Use SY3
Ideal Situations
- Understand system-wide interactions and feedback loops
- Detect patterns that emerge across components
- Optimize for long-term system behavior, not just local gains
Trigger Questions
- "How can we use Stocks & Flows here?"
- "What changes if we apply SY3 to this analyzing coordination patterns across teams?"
- "Which assumptions does SY3 help us surface?"
The SY3 Process
Step 1: Define the focus
// Using SY3 (Stocks & Flows) - Establish the focus
const focus = "Distinguish accumulations from rates of change affecting them";
Step 2: Apply the model
// Using SY3 (Stocks & Flows) - Apply the transformation
const output = applyModel("SY3", focus);
Step 3: Synthesize outcomes
// Using SY3 (Stocks & Flows) - Capture insights and decisions
const insights = summarize(output);
Practical Example
// Using SY3 (Stocks & Flows) - Example in a analyzing coordination patterns across teams
const result = applyModel("SY3", "Distinguish accumulations from rates of change affecting them" );
Integration with Other Transformations
- SY3 -> P1: Pair with P1 when sequencing matters.
- SY3 -> DE3: Use DE3 to validate or stress-test.
- SY3 -> IN2: Apply IN2 to compose the output.
Implementation Checklist
- Identify the context that requires SY3
- Apply the model using explicit SY3 references
- Document assumptions and outputs
- Confirm alignment with stakeholders or owners
Common Pitfalls
- Treating the model as a checklist instead of a lens
- Skipping documentation of assumptions or rationale
- Over-applying the model without validating impact
Best Practices
- Use explicit SY3 references in comments and docs
- Keep the output focused and actionable
- Combine with adjacent transformations when needed
Measurement and Success
- Clearer decisions and fewer unresolved assumptions
- Faster alignment across stakeholders
- Reusable artifacts for future iterations
Installation and Usage
Nix Installation
{
programs.moltbot.plugins = [
{ source = "github:hummbl-dev/hummbl-agent?dir=skills/SY-systems/sy3-stocks-and-flows"; }
];
}
Manual Installation
moltbot-registry install hummbl-agent/sy3-stocks-and-flows
Usage with Commands
/apply-transformation SY3 "Distinguish accumulations from rates of change affecting them"
Apply SY3 to create repeatable, explicit mental model reasoning.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?