Software Development Skills

Build or refresh .cflow/architecture.md from repository state. Use as a standalone repository-mapping entrypoint or when other Cflow skills need current architecture context before proceeding.

Turn a feature or product idea into an approved design spec before any implementation. Use only when the user explicitly asks to brainstorm, explore, or co-design an idea; never trigger it from implementation requests, bug fixes, refactor work, or other Cflow flows. Route ambiguous requests, approach questions, and worth-building judgments to cf-mr-wolf.

Find or refactor local source-file cognitive complexity hotspots while preserving behavior. Use with or without explicit file targets.

Evaluate or execute behavior-preserving local regrouping of already-related files into a cohesive feature or workflow slice. Use when the problem is navigation cost, placement, scattered files, feature-slice cohesion, or whether related files should live together.

Generate or review documentation for accuracy against the code, conceptual duplication across and within files, verbosity, and structural drift. Use when writing, updating, auditing, trimming, or fact-checking Markdown docs, READMEs, or architecture and design notes, or when docs may be out of sync with the code. Do not use for prose grammar linting alone; route structural code grouping to cf-cohesion.

Clarify ambiguous problem framing before implementation or Cflow assessment. Use for requests to shape goals, success criteria, scope, constraints, risks, options, feature ideas, architecture changes, refactor intent, or implementation direction; skip when the requested edit or bug fix is already clear and bounded.

Frame, validate, or explain a bug, code change, architectural concern, or behavior through concrete code-grounded scenarios. Use when the user or another agent needs to understand real impact across direct and indirect flows, especially before a fix or after an implementation.

Diagnose overengineering, file sprawl, unnecessary lifecycle complexity, and whether an area can be made substantially cleaner by simplifying behavior, interface contracts, boundaries, or architecture. Use when the current request questions whether files are necessary, suspects overengineering, wants a large simplification refactor, or asks whether to remove/replace an over-complex design instead of polishing it.

Evaluate or execute a behavior-preserving file-level split from one source file into nearby owned files. Use when the current request asks whether a file should be split or asks to perform a scoped extraction into files.

Assess, plan, execute, review, verify, or resume cleanup and refactor work in Cflow. Use for repository-level cleanup/refactor assessment, architecture or structure evaluation, artifact-backed workflows, bounded work units, and resume from existing .cflow state; route unclear framing to cf-mr-wolf and missing or stale architecture maps to cf-architecture.

Create or maintain a lightweight todo file tracking next steps and open questions from an analysis or working session. Use when the request asks to write, update, check off, or clean a todo.md, or to track remaining work or points to investigate before deciding. Do not use for Cflow refactor progress or resume state (cf-start owns them), decision framing (cf-mr-wolf), or project documentation (cf-docs).

Reconstruct and audit an execution, product, or refactor path from repository evidence. Use to identify broken sequences, missing states, unclear ownership, unsafe ordering, weak invariants, failure modes, resume gaps, or test gaps before changing code.