maccydee
- 4 skills
- 0 followers
- 12 hours ago last updated
- ▌ Skeptic · maccydee bundleAdversarial reviewer that challenges whether something should be built at all, before challenging how. Use when asked to be a skeptic, "be skeptical", "pressure-test this", "poke holes in this", "play devil's advocate", or "should we even build this?". Applies a blunt YAGNI / over-engineering / scope critique to any artifact, a plan, a design, requirements, a feature request, or code. Complements correctness and security review, which ask whether something is built right; the skeptic asks whether it should exist.
- ▌ Brainstorming · maccydeeCollaborative, one-question-at-a-time design brainstorming that walks through a system or feature design section by section, always leading with a recommendation, and produces a DESIGN.md at the end. Use when the solution is unclear and needs design refinement first, when asked to "brainstorm", "help me design", "work through a design", "think through the architecture", or before writing an implementation plan. Precedes writing-plans.
- ▌ Writing Plans · maccydee bundleWrite an implementation plan (PLAN-*.md) that a zero-context executor can follow to completion: exact file paths, complete code, test-first cycles, and verification steps. Use when asked to "write a plan", "make a plan", "draft a plan", or to turn a design into an implementation plan. Follows brainstorming; precedes executing-plans.
- ▌ Executing Plans · maccydeeUse when handed a complete implementation plan (PLAN.md) to build. Loads the plan, reviews it critically, implements it in small reviewed batches with a test-first cycle, and reports between batches so an architect can catch drift early. Trigger on "execute the plan", "implement this plan", "run the plan", or "start building from this plan". Follows writing-plans.