mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-03-05 16:13:08 +08:00

Files

catlog22 bbdd1840de Add document standards, quality gates, and templates for team lifecycle phases

- Introduced `document-standards.md` to define YAML frontmatter schema, naming conventions, and content structure for spec-generator outputs.
- Created `quality-gates.md` outlining per-phase quality gate criteria and scoring dimensions for spec-generator outputs.
- Added templates for architecture documents, epics and stories, product briefs, and requirements PRD to streamline documentation in respective phases.

2026-03-04 23:54:20 +08:00

3.0 KiB

Raw Blame History

prefix, inner_loop, additional_members, message_types

prefix

inner_loop

additional_members

message_types

EXPLORE

false

success	error
exploration_ready	error

Codebase Explorer

Explore codebase structure through cli-explore-agent, collecting structured context (files, patterns, findings) for downstream analysis. One explorer per analysis perspective.

Phase 2: Context & Scope Assessment

Input	Source	Required
Task description	From task subject/description	Yes
Session path	Extracted from task description	Yes

Extract session path, topic, perspective, dimensions from task description:

Field	Pattern	Default
sessionFolder	`session:\s*(.+)`	required
topic	`topic:\s*(.+)`	required
perspective	`perspective:\s*(.+)`	"general"
dimensions	`dimensions:\s*(.+)`	"general"

Determine exploration number from task subject (EXPLORE-N)
Build exploration strategy by perspective:

Perspective	Focus	Search Depth
general	Overall codebase structure and patterns	broad
technical	Implementation details, code patterns, feasibility	medium
architectural	System design, module boundaries, interactions	broad
business	Business logic, domain models, value flows	medium
domain_expert	Domain patterns, standards, best practices	deep

Phase 3: Codebase Exploration

Use CLI tool for codebase exploration:

Bash({
  command: `ccw cli -p "PURPOSE: Explore codebase for <topic> from <perspective> perspective; success = structured findings with relevant files and patterns
TASK: • Run module depth analysis • Search for topic-related patterns • Identify key files and their relationships • Extract architectural insights
MODE: analysis
CONTEXT: @**/* | Memory: Session <session-folder>, perspective <perspective>
EXPECTED: JSON output with: relevant_files (path, relevance, summary), patterns, key_findings, module_map, questions_for_analysis, _metadata (perspective, search_queries, timestamp)
CONSTRAINTS: Focus on <perspective> angle - <strategy.focus> | Write to <session>/explorations/exploration-<num>.json
" --tool gemini --mode analysis --rule analysis-analyze-code-patterns`,
  run_in_background: false
})

ACE fallback (when CLI produces no output):

mcp__ace-tool__search_context({ project_root_path: ".", query: "<topic> <perspective>" })

Phase 4: Result Validation

Check	Method	Action on Failure
Output file exists	Read output path	Create empty result, run ACE fallback
Has relevant_files	Array length > 0	Trigger ACE supplementary search
Has key_findings	Array length > 0	Note partial results, proceed

Write validated exploration to <session>/explorations/exploration-<num>.json.

Update <session>/wisdom/.msg/meta.json under explorer namespace:

Read existing -> merge { "explorer": { perspective, file_count, finding_count } } -> write back

3.0 KiB Raw Blame History

Codebase Explorer

Phase 2: Context & Scope Assessment

Phase 3: Codebase Exploration

Phase 4: Result Validation

3.0 KiB

Raw Blame History