Request Enhancer Skill v2.0

Purpose

This skill automatically transforms user requests into well-structured, detailed prompts that follow best practices for vibe coding and SaaS development. It enhances clarity, adds context, and structures requests for optimal AI assistance.

Key Improvements in v2.0:

• Integrated with CleanConnect memory bank system
• Enhanced business focus for non-technical founder
• Automatic V1 checklist mapping
• Risk assessment and mitigation strategies
• Progress tracking integration

Enhancement Process

1. Request Analysis

• Identify the core intent and objectives
• Detect implicit requirements and assumptions
• Assess technical complexity and domain
• Identify missing context that would be helpful

2. Linguistic Enhancement

• Improve clarity and specificity
• Add proper technical terminology where appropriate
• Structure sentences for unambiguous interpretation
• Ensure professional yet approachable tone

3. Structural Improvements

• Add clear objectives and success criteria
• Include relevant context about the project/environment
• Specify constraints and preferences
• Organize into logical sections with clear headings

4. Best Practices Integration

• Include relevant architectural considerations
• Add security and performance implications
• Suggest testing strategies
• Reference project-specific standards and patterns

Enhanced Request Template v2.0

markdown
1## Objective
2[Clear, specific statement of what needs to be accomplished]
3
4## Business Context
5- **User**: Non-technical founder building CleanConnect SaaS
6- **Goal**: [Business outcome this enables]
7- **Impact**: [Why this matters for the business]
8- **Timeline**: [Urgency level: Immediate/This week/Soon]
9
10## Project Context
11- **Project**: CleanConnect - Multi-tenant SaaS for workforce management
12- **Tech Stack**: Hono + Supabase + React + TypeScript + pnpm
13- **Current Phase**: [Foundation/V1 Build/V2]
14- **Recent Progress**: [What was just completed]
15
16## V1 Checklist Mapping
17- **Checklist Item**: [Exact item from plan/]
18- **Phase Number**: [Current phase from plan/PLAN_INDEX.md]
19- **Complexity**: [Simple/Medium/Complex]
20- **Estimated Time**: [Time estimate in hours]
21- **Dependencies**: [What needs to be done first]
22
23## Requirements
24### Must-Haves (Non-negotiable)
25- [Critical requirements that must be met]
26
27### Should-Haves (Important)
28- [Important features that should be included]
29
30### Could-Haves (Nice to have)
31- [Optional features if time permits]
32
33## Technical Constraints
34- Must follow Zapier-style layering
35- All database queries scoped by organizationId
36- No vendor SDK calls outside adapters/
37- Use fixed tech stack only
38- Validate inputs with Zod
39
40## Risk Assessment
41- **Risk Level**: [Low/Medium/High]
42- **Potential Issues**: [What could go wrong]
43- **Mitigation**: [How we'll prevent problems]
44- **Confidence**: [1-10 confidence level]
45
46## Success Criteria
47- [Measurable outcomes that indicate success]
48- [How to verify the implementation works]
49- [What the user should be able to do]
50
51## Testing Strategy
52- **Unit Tests**: [What needs unit testing]
53- **Integration Tests**: [What needs integration testing]
54- **Manual Testing**: [How to manually verify]
55
56## Next Steps
571. [Immediate first action]
582. [What needs to be decided]
593. [What I need from you]

Implementation Guidelines v2.0

When enhancing requests:

1. Founder-First Communication:

   • Use simple, non-technical language
   • Focus on business outcomes
   • Provide confidence levels
   • Celebrate small wins

2. Memory Integration:

   • Check activeContext.md for current work
   • Reference previous decisions
   • Maintain continuity
   • Update memory after completion

3. Risk-Aware Planning:

   • Always assess risk level
   • Provide mitigation strategies
   • Flag potential blockers early
   • Offer backup options

4. Architecture Compliance:

   • Enforce Zapier-style layering
   • Ensure tenant scoping
   • Use fixed tech stack
   • Follow established patterns

5. Progress Tracking:

   • Map to V1 checklist
   • Estimate complexity realistically
   • Track completion percentage
   • Document lessons learned

Example Transformations

Before:

"make a user login thing"

After:

markdown
1## Objective
2Implement a secure user authentication system with login and registration functionality for the CleanConnect SaaS platform.
3
4## Context
5- Project: CleanConnect - Multi-tenant SaaS for workforce management
6- Tech Stack: Hono (backend) + Supabase (database/auth) + React (frontend) + TypeScript
7- Current State: Basic project structure exists, Supabase configured
8- Business Impact: Critical for user onboarding and data security
9
10## Requirements
11### Functional Requirements
12- User registration with email verification
13- Login with email/password
14- Password reset functionality
15- Session management with JWT tokens
16- Multi-tenant isolation by organizationId
17
18### Technical Requirements
19- Use Supabase Auth for authentication
20- Implement RLS policies for data isolation
21- Secure session handling with httpOnly cookies
22- Rate limiting on auth endpoints
23- OAuth providers (Google, Microsoft) for enterprise
24
25### Constraints
26- Must follow existing authentication patterns in AGENTS.md
27- All database queries must be scoped by organizationId
28- No vendor SDK calls outside adapters layer
29
30## Success Criteria
31- Users can register and verify email
32- Login works with correct credentials
33- Invalid attempts are properly handled
34- Sessions persist correctly across refreshes
35- Data isolation between organizations is enforced
36
37## Preferred Approach
38- Follow the authentication flow outlined in docs/ARCHITECTURE_BLUEPRINT.md
39- Use Zod for input validation
40- Implement proper error handling with stable error codes
41- Add comprehensive logging for security events
42
43## Testing Strategy
44- Unit tests for auth utilities
45- Integration tests for login/registration flows
46- Security tests for common vulnerabilities
47- Test multi-tenant data isolation

Automatic Invocation

CRITICAL: This skill runs AUTOMATICALLY on EVERY user message before any other processing.

This skill is triggered:

• On ALL user messages (no exceptions)
• Before any other tool or skill runs
• Even for seemingly simple requests

The only exceptions are:

• Messages starting with /no-enhance
• Messages to other agents/skills that explicitly bypass enhancement

Enhancement Rules for CleanConnect v2.0

Mandatory Fields to Add:

1. Business Context: Why this matters for the founder
2. Risk Assessment: Risk level and mitigation strategies
3. Phase Number: From plan/PLAN_INDEX.md (not just V1)
4. Dependencies: What needs to be done first
5. Confidence Level: 1-10 scale for success

Auto-Correction Logic:

• If request is vague → Enhance with business context
• If request lacks risk → Add risk assessment
• If request jumps ahead → Realign to current phase
• If request is too broad → Break into smaller tasks
• If request lacks testing → Add comprehensive testing strategy
• If request ignores constraints → Add technical constraints section

Memory Integration:

• Check .windsurf/active/activeContext.md for current work
• Reference previous decisions from memory bank
• Maintain continuity across sessions
• Update memory after task completion

Founder-Friendly Output:

• Use analogies instead of technical terms
• Focus on outcomes and business value
• Provide clear next steps
• Include celebration points for progress

Notes

• This skill runs before any other processing
• The enhanced request becomes the new prompt for Cascade
• Users can still manually invoke with @request-enhancer
• Enhancements are conservative - when in doubt, keep it simple
• v2.0 includes improved business focus and risk management
• Integrated with memory bank for context continuity
• Designed specifically for non-technical founder workflow

Version History

• v1.0: Initial implementation with basic enhancement
• v2.0: Added business focus, risk assessment, memory integration, and founder-friendly communication