flowsim

Trace plan claims through code and report execution mismatches.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/exerias21/brainstorm-toolkit --skill flowsim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flowsim
Source: https://github.com/exerias21/brainstorm-toolkit/tree/main/skills/flowsim
Command: npx skills add https://github.com/exerias21/brainstorm-toolkit --skill flowsim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trace claims in plans or tasks through the actual source code and surface mismatches in the resulting execution narrative. It enables structured code-review passes that reveal where the implementation diverges from the plan, improving the reliability of sdlc cycles.

Core Features & Use Cases

  • Narrative flow tracing: map each claimed flow to concrete code anchors and report mismatches.
  • Adjustable tracing scope: supports --max-hops, --focus, and --force to control depth and focus.
  • Re-trace and cache: re-use prior traces when code hasn't changed to save time across fix loops.
  • Eval and test integration: correlate with eval results and tests to validate flow correctness.
  • Plan-to-code validation in /sdlc workflows: run after feature implementation to ensure alignment.

Quick Start

Run flowsim with a plan file or task reference to begin tracing the end-to-end flow through the codebase.

Frequently Asked Questions about flowsim

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

FAQPage Schema
How do I trace a plan through my codebase to find implementation gaps?

You trace plan-vs-code mismatches by consuming a plan file or task reference and mapping claimed flows to concrete code anchors. The trace reports mismatches where actual code execution diverges from the intended implementation narrative.

What is plan-vs-code validation in SDLC workflows?

Plan-vs-code validation in SDLC workflows is the process of tracing claimed flows through actual source code after feature implementation. It ensures implementation alignment by surfacing mismatches between the planned execution narrative and the written code anchors.

How do I control tracing depth and scope across a large codebase?

Control tracing depth and scope using the --max-hops, --focus, and --force options. These parameters adjust how deeply the trace traverses the codebase and allow targeted analysis of specific execution flows during ad hoc investigations.

Can I reuse previous traces when source code has not changed?

Yes, flowsim supports re-tracing and caching to reuse prior traces when code hasn't changed. This saves time across fix loops by avoiding redundant tracing operations during repeated plan-to-code validation passes.

Does plan-to-code tracing integrate with eval results and tests?

Yes, plan-to-code tracing correlates with eval results and tests to validate flow correctness. This integration ensures that the traced execution narrative aligns with actual test outcomes and evaluation metrics across the codebase.

When should I run plan-vs-code validation during feature implementation?

Run plan-vs-code validation after feature implementation within SDLC workflows to ensure alignment. It performs a structured code-review pass that reveals where the implementation diverges from the plan, improving overall cycle reliability.