skills/dmjgilbert/subagent-development/SKILL.md
Execute plans using fresh subagent per task with code review between tasks. Use for high-quality iterative implementation.
npx skillsauth add aiskillstore/marketplace subagent-developmentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Fresh subagent per task + review between tasks = high quality, fast iteration.
1. Read the plan document
2. Create TodoWrite with all tasks
3. Verify plan is sound before starting
Dispatch Implementation Subagent:
Task([appropriate-agent], prompt="
Implement Task N from the plan:
**Task:** [Task description]
**Requirements:**
- Follow TDD (write failing test first)
- Implement minimal code to pass
- Verify all tests pass
- Commit with descriptive message
**Output:**
- What was implemented
- Test results
- Any issues encountered
")
After EACH task, dispatch reviewer:
Task(code-reviewer, prompt="
Review implementation of Task N:
**What was implemented:** [From subagent output]
**Commits:** [Range]
**Requirements:** [From plan]
Evaluate:
- Implementation vs requirements match
- Code quality and patterns
- Test coverage
- Critical/Important/Minor issues
")
| Severity | Action | | -------- | --------------------------- | | Critical | Fix immediately, re-review | | High | Fix before next task | | Medium | Fix if quick, else document | | Low | Document for later |
After all tasks complete:
Task(code-reviewer, prompt="
Final review of complete implementation:
**Plan:** [Reference]
**All commits:** [Full range]
Verify:
- Complete plan compliance
- Architectural soundness
- No regressions
- Ready for merge
")
Transition to merge/PR workflow.
## Task N Review
**Status:** [Pass/Fail]
### Critical Issues
[None / List]
### High Priority
[None / List]
### Medium Priority
[None / List]
### Minor/Suggestions
[None / List]
### Verdict
- [ ] Proceed to next task
- [ ] Fix issues first
- [ ] Needs discussion
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.