Michaelxwb/code_flow

AI开发spec

11Stars on the repository
32Mods indexed here, across every type
9d agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied

cf-init

01

Michaelxwb/code_flow

Skill Claude CodeCodex

Initialize the code-flow spec system in a project. Use when setting up .code-flow/ directory, generating spec files, configuring Codex hooks (.codex/hooks.json), creating AGENTS.md, or bootstrapping coding standards for a new or existing project.

11 9d ago A 55 tokens

cf-learn

02

Michaelxwb/code_flow

Skill Claude CodeCodex

Scan project configs, current workspace changes, and code patterns to extract evidence-backed coding standards and retrieval maps. Use for cf-learn, cf-learn --map, cf-learn --review, or when updating specs from existing conventions.

11 9d ago A 51 tokens

cf-spec

03

Michaelxwb/code_flow

Skill Claude CodeCodex

Manage schema-v1 Spec Context, drift recovery, and prepared one-shot migration plans.

11 9d ago A 20 tokens

cf-stats

04

Michaelxwb/code_flow

Skill Claude CodeCodex

Show token usage statistics for the spec system (per-file breakdown, budget utilization, L0/L1 tiers, compression, qualityloop health); --audit adds a spec quality audit. Use when checking token usage, budget, spec system health, or spec quality issues. Replaces the former cf-scan.

11 9d ago A 65 tokens

cf-sync

05

Michaelxwb/code_flow

Skill Claude CodeCodex

One-command canonical → deploy sync for dual-copy artifacts, with drift check.

11 9d ago A 18 tokens

cf-task-align

06

Michaelxwb/code_flow

Skill Claude CodeCodex

Generate a design brief (.design.md) from a requirement through structured interactive dialogue. Accepts plain text, an existing PRD (.prd.md) to derive from, or a .design.md draft to resume. Adapts to the nature of the work — feature development, refactoring, CLI tools, background jobs, performance optimization, etc.

11 9d ago A 73 tokens

cf-task-archive

07

Michaelxwb/code_flow

Skill Claude CodeCodex

Archive a completed task file after completeness, correctness, traceability, and consistency validation. Use when all subtasks are done and you want to archive the task file and check for spec updates.

11 9d ago A 43 tokens

cf-task-block

08

Michaelxwb/code_flow

Skill Claude CodeCodex

Mark a subtask as blocked with a reason. Use when a task cannot proceed due to external dependency, missing information, pending design decision, or unresolved question.

11 9d ago A 36 tokens

cf-task-graph

09

Michaelxwb/code_flow

Skill Claude CodeCodex

Visualize task dependency DAG, identify parallelizable task groups and critical path. Use when planning execution order, understanding task dependencies, or deciding which tasks can run concurrently.

11 9d ago A 38 tokens

cf-task-note

10

Michaelxwb/code_flow

Skill Claude CodeCodex

A review-note format for marking an issue directly in the file being reviewed, using a `#NOTES` marker. The description does not provide the complete note format.

11 9d ago A 5 tokens

cf-task-plan

11

Michaelxwb/code_flow

Skill Claude CodeCodex

Break down a design document or design brief into structured task files with atomic subtasks, priorities, dependencies, and source chapter references. Use when starting work on a new feature from a design doc or a .design.md brief produced by cf-task-align.

11 9d ago A 54 tokens

cf-task-prd

12

Michaelxwb/code_flow

Skill Claude CodeCodex

Generate a Product Requirements Document (PRD) from a one-liner requirement through structured interactive dialogue. Use when starting from a vague idea without a clear PRD document. The output feeds cf-task-align for technical design.

11 9d ago A 49 tokens

cf-task-status

14

Michaelxwb/code_flow

Skill Claude CodeCodex

Show task status overview: subtask states, progress percentages, blocked items, and overall completion. Use when checking task progress, what's done, what's blocked, or what needs to be done next.

11 9d ago A 43 tokens

cf-validate

15

Michaelxwb/code_flow

Skill Claude CodeCodex

Run validation rules (lint, type check, tests) against changed files based on .code-flow/validation.yml. Auto-fix failures. Use when validating code changes, running project checks, or after editing source files.

11 9d ago A 48 tokens