| name | software-dev |
| description | Software development workflow patterns: exploration, implementation, testing, review cycles. Load this skill when coordinating multi-step development tasks or delegating software work. |
Software Development Workflow
Patterns for coordinating software development from requirements to shipped code.
<core_loop>
- Understand — explore codebase structure, read relevant files, identify patterns and conventions
- Plan — decompose into atomic tasks, identify dependencies, map to appropriate agents/tiers
- Implement — write code following existing conventions, handle edge cases, add tests
- Verify — run tests, lint, type-check, build. Fix failures immediately
- Review — check quality, correctness, maintainability. Load review-workflow skill if thorough review needed
- Commit — atomic commits with descriptive messages, one logical change per commit
</core_loop>
<delegation_patterns>
Task Granularity
- ONE atomic task per subagent session
- If tasks touch different files/modules/concerns → separate delegations
- Task granularity maps to atomic commits
Tier Selection
- quick: isolated, well-defined tasks with complete context. Single functions, config changes, simple edits
- agent: complex implementation requiring judgment. Multi-file changes, integrations, debugging
- expert: architectural decisions, novel algorithms, complex multi-system coordination
Parallel vs Sequential
- Batch independent tasks that touch different files/modules
- Sequence tasks with dependencies or overlapping files
- Follow parallel batches with a verification pass
</delegation_patterns>
<verification_strategy>
- After implementation: run the project's test suite
- After refactoring: run full test suite + lint + type-check
- After bug fixes: run the specific failing test first, then full suite
- Before committing: verify build succeeds
</verification_strategy>
<commit_hygiene>
- Atomic commits: one logical change per commit
- Descriptive messages: explain what and why, not how
- Keep the codebase in a working state after every commit
- Keep refactoring and feature additions in separate commits
</commit_hygiene>
<failure_handling>
- Test failures → delegate to agent (general) or expert (complex/elusive bugs). Load debug-workflow skill
- Build failures → delegate to agent with error output
- Review issues → delegate fixes as separate atomic tasks
- Handle each failure individually rather than bundling fixes together
</failure_handling>
