skills/dmjgilbert/executing-plans/SKILL.md
Execute implementation plans with batch processing and review checkpoints. Use when given a plan document.
npx skillsauth add aiskillstore/marketplace executing-plansInstall 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.
Execute implementation plans systematically with quality gates between batches.
If issues found: Stop and clarify before proceeding
Default batch size: 3 tasks
For each task in batch:
in_progresscompleted only when verifiedAfter completing a batch:
## Batch Complete
**Tasks Completed:** [List]
**Verifications:**
- Task 1: [Pass/Fail] - [Details]
- Task 2: [Pass/Fail] - [Details]
- Task 3: [Pass/Fail] - [Details]
**Issues Found:** [If any]
Ready for feedback.
After all tasks finished and verified:
When blocked: Ask for clarification, don't force through.
| Scenario | Batch Size | | ----------------- | ------------ | | Simple tasks | 3-5 | | Complex tasks | 1-2 | | High-risk changes | 1 | | User preference | As specified |
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.