refactor: enhance Codex output standards with structured templates

- Add Format Priority section aligned with GEMINI.md style
- Expand default output formats into three comprehensive templates:
  * Single Task Implementation (with Summary, Key Decisions, Testing, Validation)
  * Multi-Task Execution (First Subtask and Subsequent Subtasks with context passing)
  * Partial Completion (with Blocked/Required/Recommendation sections)
- Add Code References section with standardized format
- Standardize Related Files section at output beginning
- Improve clarity and consistency with Gemini execution protocol

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
catlog22
2025-10-16 13:51:42 +08:00
parent 39a35c24b1
commit d2d9f16673

View File

@@ -124,52 +124,131 @@ RULES: [templates | additional constraints]
chcp 65001 > $null chcp 65001 > $null
``` ```
## Output Format ## Output Standards
### Format Priority
**If template defines output format** → Follow template format EXACTLY (all sections mandatory)
**If template has no format** → Use default format below based on task type
### Default Output Formats
#### Single Task Implementation
### Related Files (At Beginning)
```markdown ```markdown
# Implementation: [TASK Title]
## Changes ## Changes
- Created: `path/to/file1.ext` (X lines) - Created: `path/to/file1.ext` (X lines)
- Modified: `path/to/file2.ext` (+Y/-Z lines) - Modified: `path/to/file2.ext` (+Y/-Z lines)
- Deleted: `path/to/file3.ext` - Deleted: `path/to/file3.ext`
```
### Completion Status ## Summary
[2-3 sentence overview of what was implemented]
**Single Task Success**: ## Key Decisions
``` 1. [Decision] - Rationale and reference to similar pattern
✅ Task completed 2. [Decision] - path/to/reference:line
Validation: ## Implementation Details
[Evidence-based description with code references]
## Testing
- Tests written: X new tests
- Tests passing: Y/Z tests
- Coverage: N%
## Validation
✅ Tests: X passing ✅ Tests: X passing
✅ Coverage: Y% ✅ Coverage: Y%
✅ Build: Success ✅ Build: Success
Next Steps: [recommendations] ## Next Steps
[Recommendations or future improvements]
``` ```
**Subtask Success**: #### Multi-Task Execution (with Resume)
```
✅ Subtask N/M completed
Integration: **First Subtask**:
✅ Compatible with previous subtasks ```markdown
# Subtask 1/N: [TASK Title]
## Changes
[List of file changes]
## Implementation
[Details with code references]
## Testing
✅ Tests: X passing ✅ Tests: X passing
✅ Integration: Compatible with existing code
Context for next subtask: ## Context for Next Subtask
- [Key decisions made] - Key decisions: [established patterns]
- [Files created/modified] - Files created: [paths and purposes]
- [Patterns established] - Integration points: [where next subtask should connect]
``` ```
**Partial Completion**: **Subsequent Subtasks**:
``` ```markdown
⚠️ Task partially completed # Subtask N/M: [TASK Title]
Completed: [what worked] ## Changes
Blocked: [what failed, root cause] [List of file changes]
Required: [what's needed]
Recommendation: [next steps] ## Integration Notes
✅ Compatible with subtask N-1
✅ Maintains established patterns
✅ Tests pass with previous work
## Implementation
[Details with code references]
## Testing
✅ Tests: X passing
✅ Total coverage: Y%
## Context for Next Subtask
[If not final subtask, provide context for continuation]
```
#### Partial Completion
```markdown
# Task Status: Partially Completed
## Completed
- [What worked successfully]
- Files: `path/to/completed.ext`
## Blocked
- **Issue**: [What failed]
- **Root Cause**: [Analysis of failure]
- **Attempted**: [Solutions tried - attempt X of 3]
## Required
[What's needed to proceed]
## Recommendation
[Suggested next steps or alternative approaches]
```
### Code References
**Format**: `path/to/file:line_number`
**Example**: `src/auth/jwt.ts:45` - Implemented token validation following pattern from `src/auth/session.ts:78`
### Related Files Section
**Always include at output beginning** - List ALL files analyzed, created, or modified:
```markdown
## Related Files
- `path/to/file1.ext` - [Role in implementation]
- `path/to/file2.ext` - [Reference pattern used]
- `path/to/file3.ext` - [Modified for X reason]
``` ```
## Error Handling ## Error Handling