5d-refine
Stress-test the plan through adversarial review and edge case analysis. Use when: (1) After PLAN phase in 5D-SDD workflow, (2) User wants to 'validate,' 'review,' or 'check' a plan, (3) Before committing significant resources to implementation, (4) Plan exists but hasn't been challenged. This phase catches plan-level errors before they become code-level errors.
What this skill does
# REFINE Phase Stress-test the plan before committing to specification. ## Stress Test Methods ### 1. Inversion Attack Argue against the plan: - "Here's why this will fail: [reasons]" - "The hidden dependencies are: [list]" - "This assumes X, but what if X is false?" Force the user to defend or amend. ### 2. Edge Case Probing For each core behavior, ask: - "What happens when [unusual input]?" - "What if [dependency] is unavailable?" - "How does this behave at [scale extreme]?" Document answers or flag as "needs resolution." ### 3. Stakeholder Simulation Roleplay different perspectives: **Skeptical Engineer:** "This seems over-engineered. Why not just [simpler approach]?" **Impatient PM:** "When will this ship? What's the MVP?" **Confused User:** "I don't understand how to [core action]." **Ops On-Call:** "How do I debug this at 3am?" ### 4. Dependency Audit (Height) List everything the plan depends on: - External services - Team knowledge/skills (what capabilities must exist?) - User behaviors - Business conditions - Adjacent domain skills that might block progress Rate each: stable / risky / unknown ### 5. Quadrant Stress Test Probe each quadrant for weaknesses: | Quadrant | Stress Question | |----------|-----------------| | Individual Inner | "What understanding gaps exist?" | | Collective Inner | "Where might stakeholders disagree?" | | Individual Outer | "What artifacts are under-specified?" | | Collective Outer | "What system constraints are ignored?" | ### 6. Time Trajectory Check - "How have similar plans failed historically?" - "What's changing in this domain that affects the plan?" - "Does this plan transcend and include current approaches, or just replace them?" ### 7. Level Check (Depth) Ask yourself: Is refinement improving the plan, or is the user defending their original idea with better words? Signs of defensive refinement: - Adding complexity to protect core assumptions - Dismissing objections rather than addressing them - "That won't happen" without evidence If defensive: return to SPAR. ## Output Format ``` ## Refinement Summary **Stress tests passed:** - [test]: [how addressed] **Edge cases documented:** - [case]: [planned handling] **Dependency risks:** - [dependency]: [risk level] - [mitigation] **Plan amendments:** - [change made based on refinement] **Unresolved issues:** - [issue]: [why deferred / needs more info] **Ready for SPEC phase:** [yes/no] ``` ## Exit Criteria Proceed to SPEC when: - Major objections have responses (not dismissals) - Edge cases are documented (even if handling is "error out") - No high-risk dependencies without mitigation - Plan text has been updated with refinements
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.