mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-12 02:37:45 +08:00
1073e43c0b
- Split task-json-schema.txt into two mode-specific templates: - task-json-agent-mode.txt: Agent execution (no command field) - task-json-cli-mode.txt: CLI execution (with command field) - Update task-generate.md: - Remove outdated Codex resume mechanism description - Add clear execution mode examples (Agent/CLI) - Simplify CLI Execute Mode Details section - Update task-generate-agent.md: - Add --cli-execute flag support - Command selects template path before invoking agent - Agent receives template path and reads it (not content) - Clarify responsibility: Command decides, Agent executes - Improve architecture: - Clear separation: Command layer (template selection) vs Agent layer (content generation) - Template selection based on flag, not agent logic - Agent simplicity: receives path, reads template, generates content 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
120 lines
4.4 KiB
Plaintext
120 lines
4.4 KiB
Plaintext
Task JSON Schema - Agent Mode (No Command Field)
|
|
|
|
## Schema Structure
|
|
|
|
```json
|
|
{
|
|
"id": "IMPL-N[.M]",
|
|
"title": "Descriptive task name",
|
|
"status": "pending",
|
|
"meta": {
|
|
"type": "feature|bugfix|refactor|test|docs",
|
|
"agent": "@code-developer|@test-fix-agent|@general-purpose"
|
|
},
|
|
"context": {
|
|
"requirements": ["extracted from analysis"],
|
|
"focus_paths": ["src/paths"],
|
|
"acceptance": ["measurable criteria"],
|
|
"depends_on": ["IMPL-N"],
|
|
"artifacts": [
|
|
{
|
|
"type": "synthesis_specification",
|
|
"path": "{synthesis_spec_path}",
|
|
"priority": "highest",
|
|
"usage": "Primary requirement source - use for consolidated requirements and cross-role alignment"
|
|
},
|
|
{
|
|
"type": "role_analysis",
|
|
"path": "{role_analysis_path}",
|
|
"priority": "high",
|
|
"usage": "Technical/design/business details from specific roles. Common roles: system-architect (ADRs, APIs, caching), ui-designer (design tokens, layouts), product-manager (user stories, metrics)"
|
|
}
|
|
]
|
|
},
|
|
"flow_control": {
|
|
"pre_analysis": [
|
|
{
|
|
"step": "load_synthesis_specification",
|
|
"action": "Load consolidated synthesis specification",
|
|
"commands": [
|
|
"Read({synthesis_spec_path})"
|
|
],
|
|
"output_to": "synthesis_specification",
|
|
"on_error": "fail"
|
|
},
|
|
{
|
|
"step": "load_context_package",
|
|
"action": "Load context package for project structure",
|
|
"commands": [
|
|
"Read({context_package_path})"
|
|
],
|
|
"output_to": "context_pkg",
|
|
"on_error": "fail"
|
|
},
|
|
{
|
|
"step": "mcp_codebase_exploration",
|
|
"action": "Explore codebase using MCP",
|
|
"command": "mcp__code-index__find_files(pattern=\"{file_pattern}\") && mcp__code-index__search_code_advanced(pattern=\"{search_pattern}\")",
|
|
"output_to": "codebase_structure",
|
|
"on_error": "skip_optional"
|
|
}
|
|
],
|
|
"implementation_approach": [
|
|
{
|
|
"step": 1,
|
|
"title": "Implement task following synthesis specification",
|
|
"description": "Implement '{title}' following [synthesis_specification] requirements and [context_pkg] patterns. Use synthesis-specification.md as primary source, consult artifacts for technical details.",
|
|
"modification_points": [
|
|
"Apply consolidated requirements from synthesis-specification.md",
|
|
"Follow technical guidelines from synthesis",
|
|
"Consult artifacts for implementation details when needed",
|
|
"Integrate with existing patterns"
|
|
],
|
|
"logic_flow": [
|
|
"Load synthesis specification and context package",
|
|
"Analyze existing patterns from [codebase_structure]",
|
|
"Implement following specification",
|
|
"Consult artifacts for technical details when needed",
|
|
"Validate against acceptance criteria"
|
|
],
|
|
"depends_on": [],
|
|
"output": "implementation"
|
|
}
|
|
],
|
|
"target_files": ["file:function:lines", "path/to/NewFile.ts"]
|
|
}
|
|
}
|
|
```
|
|
|
|
## Key Features - Agent Mode
|
|
|
|
**Execution Model**: Agent interprets `modification_points` and `logic_flow` to execute autonomously
|
|
|
|
**No Command Field**: Steps in `implementation_approach` do NOT include `command` field
|
|
|
|
**Context Loading**: Context loaded via `pre_analysis` steps, available as variables (e.g., [synthesis_specification], [context_pkg])
|
|
|
|
**Agent Execution**:
|
|
- Agent reads modification_points and logic_flow
|
|
- Agent performs implementation autonomously
|
|
- Agent validates against acceptance criteria
|
|
|
|
## Field Descriptions
|
|
|
|
**implementation_approach**: Array of step objects (NO command field)
|
|
- **step**: Sequential step number
|
|
- **title**: Step description
|
|
- **description**: Detailed instructions with variable references
|
|
- **modification_points**: Specific code modifications to apply
|
|
- **logic_flow**: Business logic execution sequence
|
|
- **depends_on**: Step dependencies (empty array for independent steps)
|
|
- **output**: Expected deliverable variable name
|
|
|
|
## Usage Guidelines
|
|
|
|
1. **Load Context**: Use pre_analysis to load synthesis, context package, and explore codebase
|
|
2. **Reference Variables**: Use [variable_name] to reference outputs from pre_analysis steps
|
|
3. **Clear Instructions**: Provide detailed modification_points and logic_flow for agent
|
|
4. **No Commands**: Never add command field to implementation_approach steps
|
|
5. **Agent Autonomy**: Let agent interpret and execute based on provided instructions
|