fractal-docs-generator
79Generate Directory CLAUDE.md Guides
Directory changes often leave local documentation outdated. This skill gives Claude, Codex, and Claude Code a concise pattern for refreshing directory-level CLAUDE.md files.
Capture Requirements Before Implementation
Teams lose time when vague requests become rushed implementation. This skill structures early brainstorming, compares options, and records decisions for later alignment.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "flow-brainstorming" from https://skillstore.io/skills/dimon94-flow-brainstorming.md and its manifest at https://skillstore.io/api/skills/dimon94-flow-brainstorming/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "flow-brainstorming". A user asks to add a faster search page.
Expected outcome:
The assistant asks targeted questions, defines success criteria, compares search strategies, and records the selected approach.
Using "flow-brainstorming". A team wants to refactor authentication with unclear goals.
Expected outcome:
The assistant separates security, maintainability, and user experience goals before recommending a refactor path.
Using "flow-brainstorming". A later implementation step may diverge from the original plan.
Expected outcome:
The assistant checks BRAINSTORM.md, identifies the divergence, and asks whether to update the documented decision.
The command-execution findings are false positives caused by Markdown code fences in SKILL.md examples. The entropy findings are false positives caused by readable Chinese prose and plain Markdown content; no evidence found of prompt injection, obfuscation, data exfiltration, or malicious intent.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/dimon94-flow-brainstorming/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/dimon94-flow-brainstorming?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/dimon94-flow-brainstorming?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dimon94-flow-brainstorming/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/dimon94-flow-brainstorming.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Dimon94. (2026). flow-brainstorming security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dimon94-flow-brainstorming/audits/8@techreport{dimon94-dimon94-flow-brainstorming-2026,
author = {Dimon94},
title = {flow-brainstorming security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/dimon94-flow-brainstorming/audits/8},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "flow-brainstorming security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Dimon94"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/dimon94-flow-brainstorming/audits/8"
identifiers:
- type: other
value: "skillstore:dimon94-flow-brainstorming:audit:8"
description: "Skillstore immutable audit report identifier"
Turn an initial product idea into purpose, constraints, success criteria, and candidate approaches.
Review multiple implementation strategies before choosing one and documenting the decision.
Slow down small fixes enough to capture the original need and avoid hidden assumptions.
Use flow-brainstorming for this request: {request}. Ask one clarifying question at a time before proposing a design.Use flow-brainstorming to explore two or three approaches for {feature}. Include tradeoffs and recommend one option.Use flow-brainstorming to present the proposed design for {request} in short sections. Ask for confirmation after each section.Use flow-brainstorming for REQ {id}: {title}. Capture original wording, success criteria, constraints, alternatives, decision, and alignment checks.Author
Dimon94License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
72d5025b022c77f7a51bdf5c1637c689c80e89d1
Maintenance freshness
7/20/2026
Usage
23 downloads · 199 views
File structure
📄 SKILL.md
Generate Directory CLAUDE.md Guides
Directory changes often leave local documentation outdated. This skill gives Claude, Codex, and Claude Code a concise pattern for refreshing directory-level CLAUDE.md files.
Debug Code with Root Cause Discipline
Bug fixes often fail when teams guess before they understand the cause. This skill guides Claude, Codex, and Claude Code through evidence-based debugging before implementation.
Route CC-DevFlow Workflows
Teams lose time choosing the next CC-DevFlow command during complex delivery work. This skill maps project status, phase gates, and user intent to the right Claude, Codex, or Claude Code workflow.
Review Feedback with Technical Rigor
Code review feedback can be incomplete, unclear, or incorrect. This skill helps Claude, Codex, and Claude Code verify feedback before changing code.
Refresh AI Focus During Flow Tasks
Long coding sessions can push original goals out of the model attention. This skill adds refresh checkpoints before key workflow decisions.
Enforce Test-First Task Completion
Teams can drift from test-first discipline when task files are edited by hand. This skill defines checks that block implementation completion until related tests are complete.
Track Feature Requirements in YAML
by Chemiseblanc
Teams lose project intent when requirements live only in chat or task lists. This skill keeps scope, tests, decisions, and progress in a persistent features.yml file.
Organize Conductor Tracks
by sickn33
Track work can become unclear when specs, plans, status, and metadata drift apart. This skill gives Claude, Codex, and Claude Code structured guidance for Conductor track workflows.
Plan Requirements with Interactive Questions
by DNYoussef
Ambiguous project requests often lead to missing requirements and rework. This skill guides Claude, Codex, and Claude Code through structured question batches.
Plan Creative Work Before Building
by ZhanlinCui
Teams often start implementation before goals, constraints, and trade-offs are clear. This skill guides Claude, Codex, and Claude Code through structured brainstorming before design work begins.
Stress-Test Your Plan Before Building
by mattpocock
Unresolved decisions can make a plan expensive to change during implementation. This skill interviews you systematically and recommends an answer for each decision.
Organize Long AI Tasks with Planning Files
by ZhanlinCui
Long AI sessions can lose goals, decisions, and progress. This skill guides Claude, Codex, and Claude Code to store plans, findings, and logs in project files.