mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-02-05 01:50:27 +08:00

Files

catlog22 8cdd6a8b5f Add execution and planning agent prompts, specifications, and quality standards

- Created execution agent prompt for issue execution with detailed deliverables and validation criteria.
- Developed planning agent prompt to analyze issues and generate structured solution plans.
- Introduced issue handling specifications outlining the workflow and issue structure.
- Established quality standards for evaluating completeness, consistency, correctness, and clarity of solutions.
- Defined solution schema specification detailing the required structure and validation rules for solutions.
- Documented subagent roles and responsibilities, emphasizing the dual-agent strategy for improved workflow efficiency.

2026-01-29 15:15:42 +08:00

2.7 KiB

Raw Blame History

Planning Agent Prompt

规划 agent 的提示词模板。

MANDATORY FIRST STEPS (Agent Execute)

Read role definition: ~/.codex/agents/issue-plan-agent.md (MUST read first)
Read: .workflow/project-tech.json
Read: .workflow/project-guidelines.json
Read schema: ~/.claude/workflows/cli-templates/schemas/solution-schema.json

Goal

Plan solution for issue "{ISSUE_ID}: {ISSUE_TITLE}"

Scope

CAN DO:
- Explore codebase
- Analyze issue and design solutions
- Create executable task breakdown
- Define acceptance criteria
CANNOT DO:
- Execute solutions
- Modify production code
- Make commits
Directory: {PROJECT_ROOT}

Task Description

{ISSUE_DESCRIPTION}

Deliverables

Primary Output: Solution JSON

{
  "id": "SOL-{ISSUE_ID}-1",
  "issue_id": "{ISSUE_ID}",
  "description": "Brief description of solution",
  "tasks": [
    {
      "id": "T1",
      "title": "Task title",
      "action": "Create|Modify|Fix|Refactor",
      "scope": "file path or directory",
      "description": "What to do",
      "modification_points": [...],
      "implementation": ["Step 1", "Step 2"],
      "test": {
        "commands": ["npm test -- file.test.ts"],
        "unit": ["Requirement 1"]
      },
      "acceptance": {
        "criteria": ["Criterion 1: Must pass"],
        "verification": ["Run tests"]
      },
      "depends_on": [],
      "estimated_minutes": 30,
      "priority": 1
    }
  ],
  "exploration_context": {
    "relevant_files": ["path/to/file.ts"],
    "patterns": "Follow existing pattern",
    "integration_points": "Used by service X"
  },
  "analysis": {
    "risk": "low|medium|high",
    "impact": "low|medium|high",
    "complexity": "low|medium|high"
  },
  "score": 0.95,
  "is_bound": true
}

Validation

Ensure:

All required fields present
No circular dependencies in task.depends_on
Each task has quantified acceptance.criteria
Solution follows solution-schema.json exactly
Score reflects quality (0.8+ for approval)

Return JSON

{
  "status": "completed|failed",
  "solution_id": "SOL-{ISSUE_ID}-1",
  "task_count": 3,
  "score": 0.95,
  "validation": {
    "schema_valid": true,
    "criteria_quantified": true,
    "no_circular_deps": true
  },
  "errors": []
}

Quality Standards

Completeness: All required fields, no missing sections
Clarity: Acceptance criteria must be specific and measurable
Correctness: No circular dependencies, valid schema
Pragmatism: Solution is minimal and focused

Success Criteria

✓ Solution JSON is valid and follows schema ✓ All tasks have acceptance.criteria ✓ No circular dependencies detected ✓ Score >= 0.8 ✓ Estimated total time <= 2 hours

2.7 KiB Raw Blame History