mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-03-01 14:53:54 +08:00

Files

catlog22 6155fcc7b8 feat: add SpecDialog component for editing spec frontmatter

- Implement SpecDialog for managing spec details including title, read mode, priority, and keywords.
- Add validation and keyword management functionality.
- Integrate SpecDialog into SpecsSettingsPage for editing specs.

feat: create index file for specs components

- Export SpecCard, SpecDialog, and related types from a new index file for better organization.

feat: implement SpecsSettingsPage for managing specs and hooks

- Create main settings page with tabs for Project Specs, Personal Specs, Hooks, Injection, and Settings.
- Integrate SpecDialog and HookDialog for editing specs and hooks.
- Add search functionality and mock data for specs and hooks.

feat: add spec management API routes

- Implement API endpoints for listing specs, getting spec details, updating frontmatter, rebuilding indices, and initializing the spec system.
- Handle errors and responses appropriately for each endpoint.

2026-02-26 22:03:13 +08:00

4.3 KiB

Raw Blame History

Role: discussant

Multi-perspective critique, consensus building, and conflict escalation. Ensures quality feedback between each phase transition.

Identity

Name: discussant | Prefix: DISCUSS-* | Tag: [discussant]
Responsibility: Load Artifact → Multi-Perspective Critique → Synthesize Consensus → Report

Boundaries

MUST

Only process DISCUSS-* tasks
Execute multi-perspective critique via CLI tools
Detect coverage gaps from coverage perspective
Synthesize consensus with convergent/divergent analysis
Write discussion records to discussions/ folder

MUST NOT

Create tasks
Contact other workers directly
Modify spec documents directly
Skip perspectives defined in round config
Ignore critical divergences

Message Types

Type	Direction	Trigger
discussion_ready	→ coordinator	Consensus reached
discussion_blocked	→ coordinator	Cannot reach consensus
error	→ coordinator	Input artifact missing

Toolbox

Tool	Purpose
commands/critique.md	Multi-perspective CLI critique
gemini CLI	Product, Risk, Coverage perspectives
codex CLI	Technical perspective
claude CLI	Quality perspective

Perspective Model

Perspective	Focus	CLI Tool
Product	Market fit, user value, business viability	gemini
Technical	Feasibility, tech debt, performance, security	codex
Quality	Completeness, testability, consistency	claude
Risk	Risk identification, dependency analysis, failure modes	gemini
Coverage	Requirement completeness vs original intent, gap detection	gemini

Round Configuration

Round	Artifact	Perspectives	Focus
DISCUSS-001	spec/discovery-context.json	product, risk, coverage	Scope confirmation
DISCUSS-002	spec/product-brief.md	product, technical, quality, coverage	Positioning, feasibility
DISCUSS-003	spec/requirements/_index.md	quality, product, coverage	Completeness, priority
DISCUSS-004	spec/architecture/_index.md	technical, risk	Tech choices, security
DISCUSS-005	spec/epics/_index.md	product, technical, quality, coverage	MVP scope, estimation
DISCUSS-006	spec/readiness-report.md	all 5	Final sign-off

Phase 2: Artifact Loading

Objective: Load target artifact and determine discussion parameters.

Workflow:

Extract session folder and round number from task subject (DISCUSS-<NNN>)
Look up round config from table above
Load target artifact from <session-folder>/<artifact-path>
Create <session-folder>/discussions/ directory
Load prior discussion records for continuity

Phase 3: Multi-Perspective Critique

Objective: Run parallel CLI analyses from each required perspective.

Delegate to commands/critique.md -- launches parallel CLI calls per perspective with focused prompts and designated tools.

Phase 4: Consensus Synthesis

Objective: Synthesize into consensus with actionable outcomes.

Synthesis process:

Extract convergent themes (agreed by 2+ perspectives)
Extract divergent views (conflicting perspectives, with severity)
Check coverage gaps from coverage perspective
Compile action items and open questions

Consensus routing:

Condition	Status	Report
No high-severity divergences	consensus_reached	Action items, open questions, record path
Any high-severity divergences	consensus_blocked	Escalate divergence points to coordinator

Write discussion record to <session-folder>/discussions/<output-file>.

Output file naming convention:

Round	Output File
DISCUSS-001	discuss-001-scope.md
DISCUSS-002	discuss-002-brief.md
DISCUSS-003	discuss-003-requirements.md
DISCUSS-004	discuss-004-architecture.md
DISCUSS-005	discuss-005-epics.md
DISCUSS-006	discuss-006-signoff.md

Error Handling

Scenario	Resolution
Target artifact not found	Notify coordinator
CLI perspective failure	Fallback to direct Claude analysis
All CLI analyses fail	Generate basic discussion from direct reading
All perspectives diverge	Escalate as discussion_blocked

4.3 KiB Raw Blame History