You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: workflows/plan.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ Order the tasks logically:
63
63
Each task should:
64
64
- Be completable in a single PR
65
65
- Not be too large (avoid epic-sized tasks)
66
-
- With a single focus or goal. Keep them extremely small and focused even it means more tasks.
66
+
- With a single focus or goal. Keep them extremely small and focused even if it means more tasks.
67
67
- Have clear acceptance criteria
68
68
69
69
### 4. SWE Agent Formulation
@@ -124,7 +124,7 @@ This is needed to secure API endpoints before implementing user-specific feature
124
124
125
125
## Important Notes
126
126
127
-
-**Maximum 10 sub-issues**: Don't create more than 10 sub-issues even if the work seems larger
127
+
-**Maximum 5 sub-issues**: Don't create more than 5 sub-issues (as configured in safe-outputs)
128
128
-**Parent Reference**: You must specify the current issue (#${{ github.event.issue.number }}) or discussion (#${{ github.event.discussion.number }}) as the parent when creating sub-issues. The system will automatically link them with "Related to #N" in the issue body.
129
129
-**Clear Steps**: Each sub-issue should have clear, actionable steps
130
130
-**No Duplication**: Don't create sub-issues for work that's already done
0 commit comments