skills.rest
chronista-club
chronista-clubOFFICIAL
Explore all skills by this author →
WebsiteGitHub

code-flow

Guide stakeholders through hearing-first elicitation and generate SDG-compliant SPEC.md and DESIGN.md.

1|Updated Jul 5, 2025
Search Tags:#workflow#design#documentation#requirements#spec#hearing#sdg
One-click install
npx skills add https://github.com/chronista-club/fleetflow --skill code-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-flow
Source: https://github.com/chronista-club/fleetflow/tree/main/.claude/skills/code-flow
Command: npx skills add https://github.com/chronista-club/fleetflow --skill code-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams often jump into implementation without a clear, agreed set of requirements, causing scope drift and rework. Code Flow provides a hearing-first discovery that clarifies needs and translates them into SDG artifacts (SPEC.md and DESIGN.md) to ensure the what, why, and how are captured before coding.

Core Features & Use Cases

  • Guided, step-by-step requirement elicitation using AskUserQuestion to reduce ambiguity.
  • Automated generation of SPEC.md (What & Why) and DESIGN.md (How) to document decisions and architecture.
  • Living documentation that stays synchronized with code and supports cross-project learning.
  • Pattern learning and memory integration to accelerate future work.
  • AI-assisted guidance and checklist-driven implementation support.

Quick Start

Describe your project to begin the hearing-first requirements session and let Code Flow generate SPEC.md and DESIGN.md, then guide you through implementation.

Frequently Asked Questions about code-flow

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

FAQPage Schema
How do I gather clear software requirements before starting implementation?▼

Gathering clear software requirements requires a hearing-first elicitation process that clarifies stakeholder needs and translates them into SPEC.md and DESIGN.md. This approach captures the what, why, and how before coding to minimize scope drift and rework.

What is the best way to keep project documentation synchronized with code?▼

Keeping documentation synchronized with code relies on living documents like SPEC.md and DESIGN.md that are generated from structured requirement hearings. This ensures project decisions and architecture designs stay aligned with implementation updates continuously.

How do I write SPEC.md and DESIGN.md files for software architecture planning?▼

Writing SPEC.md and DESIGN.md involves converting structured stakeholder hearings into standardized artifacts. SPEC.md captures the what and why of the project, while DESIGN.md outlines the architectural how, ensuring decisions are documented before development begins.

Can I reuse requirements and architecture decisions across different projects?▼

Reusing requirements and architecture decisions across projects is supported through pattern learning and memory integration. This feature accelerates future work by applying insights and knowledge gained from previous structured elicitation sessions to new project scopes.

Does guided requirement elicitation work for complex project scoping and architecture decisions?▼

Guided requirement elicitation works effectively for project scoping and architecture decisions by using a step-by-step AskUserQuestion workflow. This structured discovery process reduces ambiguity and ensures all stakeholder needs are accurately captured before implementation planning.

Why does my project suffer from scope drift and rework during development?▼

Project scope drift and rework typically occur when teams jump into implementation without an agreed set of clear requirements. Establishing a hearing-first discovery phase to generate SPEC.md and DESIGN.md prevents this by aligning stakeholders on scope beforehand.

Related Skills

Explore More Software Engineering Skills→
darkroomengineeringdarkroomengineering
41

discovery

Guide structured interviews to define project scope and requirements.

Official
Intermediate
xaneemxaneem
1

looped-builder

Automate planning and scaffolding of large coding tasks with generated spec, plan, prompt, and run files.

Community
Advanced
adrozdenkoadrozdenko
6

brain-debrief

Analyze brain statistics, pattern strengths, and memory topics to generate intelligence reports.

Community
Intermediate
tsuna44tsuna44

xddp.excel2md

Convert Excel USDM change specifications into synchronized Markdown documents.

Community
Intermediate