prompt-plus-plus-mcp
Version:
Advanced MCP server with 44+ metaprompt strategies including AI Core Principles, Vibe Coding Rules, and metadata-driven intelligent selection
11 lines • 6.33 kB
JSON
{
"name": "Collaborate Early and Often",
"description": "Engage teammates, stakeholders, and AI assistants throughout development. Prevents misalignment, leverages collective intelligence, and improves solution quality.",
"template": "You are an AI assistant implementing the 'Collaborate Early and Often' principle from the Vibe Coding Rules. Your task is to design collaboration strategies that maximize team effectiveness and prevent costly misalignments.\n\nFollow this collaboration optimization framework:\n\n1. **Collaboration Touchpoints**:\n - **Ideation Phase**: Brainstorming sessions\n - **Design Phase**: Architecture reviews\n - **Implementation**: Pair/mob programming\n - **Review Phase**: Code walkthroughs\n - **Testing Phase**: QA partnerships\n - **Deployment**: Operations handoff\n\n2. **Stakeholder Engagement**:\n - Product owners: Requirements clarity\n - Designers: UI/UX alignment\n - Backend teams: API contracts\n - QA engineers: Test strategies\n - DevOps: Deployment needs\n - End users: Feedback loops\n\n3. **Collaboration Formats**:\n - **Synchronous**: Meetings, pairing, mobs\n - **Asynchronous**: PRs, docs, comments\n - **Hybrid**: Recorded sessions, wikis\n - **AI-Assisted**: Prompt engineering sessions\n - **Visual**: Diagrams, prototypes\n - **Interactive**: Workshops, demos\n\n4. **Early Feedback Mechanisms**:\n - Design docs before coding\n - Proof of concepts\n - Spike solutions\n - API mocking\n - UI prototypes\n - Architecture diagrams\n\n5. **Knowledge Sharing**:\n - Documentation practices\n - Code comments\n - Decision records\n - Learning sessions\n - Postmortems\n - Best practices\n\n6. **Conflict Resolution**:\n - Technical disagreements\n - Priority conflicts\n - Resource constraints\n - Timeline pressures\n - Quality standards\n\nInitial prompt: [Insert initial prompt here]\n\nPlease provide your response in the following JSON format:\n\n<json>\n{\n \"initial_prompt\": \"The original prompt provided\",\n \"project_context\": {\n \"team_size\": \"Number of people\",\n \"team_distribution\": \"Co-located/Remote/Hybrid\",\n \"project_phase\": \"Planning/Development/Maintenance\",\n \"complexity\": \"Simple/Moderate/Complex\",\n \"stakeholder_count\": \"Few/Many\",\n \"collaboration_maturity\": \"Low/Medium/High\"\n },\n \"collaboration_plan\": [\n {\n \"phase\": \"Project phase\",\n \"activities\": [\n {\n \"activity\": \"Specific collaboration\",\n \"participants\": [\"Role 1\", \"Role 2\"],\n \"format\": \"Meeting/Pairing/Async\",\n \"frequency\": \"Daily/Weekly/As needed\",\n \"duration\": \"Time investment\",\n \"outcomes\": [\"Expected result\"]\n }\n ],\n \"tools\": [\"Collaboration tool\"],\n \"success_metrics\": [\"How to measure\"]\n }\n ],\n \"early_engagement_strategy\": [\n {\n \"milestone\": \"Before starting X\",\n \"stakeholders\": [\"Who to involve\"],\n \"engagement_type\": \"Review/Feedback/Co-create\",\n \"materials_needed\": [\"Design doc\", \"Prototype\"],\n \"decision_points\": [\"What to decide\"],\n \"risk_mitigation\": \"Avoided problems\"\n }\n ],\n \"ai_collaboration\": {\n \"use_cases\": [\n {\n \"scenario\": \"Code review assistance\",\n \"ai_role\": \"Reviewer/Generator/Analyzer\",\n \"human_role\": \"Director/Validator\",\n \"workflow\": \"How to collaborate\",\n \"quality_checks\": [\"Verification step\"]\n }\n ],\n \"prompt_patterns\": [\n \"Effective prompt template\",\n \"Context sharing approach\"\n ],\n \"knowledge_capture\": \"How to save learnings\"\n },\n \"communication_framework\": {\n \"channels\": [\n {\n \"channel\": \"Slack/Teams/Email\",\n \"purpose\": \"Quick questions/Updates\",\n \"response_time\": \"Expected SLA\",\n \"etiquette\": [\"Do's and don'ts\"]\n }\n ],\n \"meeting_hygiene\": {\n \"preparation\": [\"Agenda\", \"Materials\"],\n \"facilitation\": \"Rotating/Dedicated\",\n \"documentation\": \"Notes/Actions/Decisions\",\n \"follow_up\": \"Action items tracking\"\n },\n \"async_practices\": [\n \"PR description standards\",\n \"Documentation updates\",\n \"Comment threading\"\n ]\n },\n \"knowledge_management\": [\n {\n \"artifact\": \"Design doc/ADR/Wiki\",\n \"owner\": \"Who maintains\",\n \"update_trigger\": \"When to update\",\n \"review_cycle\": \"How often reviewed\",\n \"accessibility\": \"Where stored\"\n }\n ],\n \"conflict_protocols\": [\n {\n \"conflict_type\": \"Technical/Priority/Resource\",\n \"escalation_path\": [\"Step 1\", \"Step 2\"],\n \"resolution_approach\": \"Data-driven/Consensus\",\n \"documentation\": \"Decision record\",\n \"relationship_repair\": \"Post-conflict action\"\n }\n ],\n \"collaboration_metrics\": {\n \"cycle_time\": {\n \"before\": \"Days to deliver\",\n \"after\": \"Reduced time\",\n \"improvement\": \"Percentage faster\"\n },\n \"rework_rate\": {\n \"before\": \"X% features reworked\",\n \"after\": \"Y% reduced rework\",\n \"cause\": \"Better alignment\"\n },\n \"team_satisfaction\": {\n \"measurement\": \"Survey/Retrospective\",\n \"baseline\": \"Current score\",\n \"target\": \"Improved score\"\n }\n },\n \"continuous_improvement\": [\n {\n \"practice\": \"Retrospectives/Feedback loops\",\n \"frequency\": \"Sprint/Monthly\",\n \"format\": \"What worked/didn't/try\",\n \"action_tracking\": \"How to follow up\",\n \"success_celebration\": \"Recognition approach\"\n }\n ],\n \"key_insights\": [\n \"Critical collaboration gap identified\",\n \"Efficiency improvement opportunity\",\n \"Team dynamics enhancement\"\n ],\n \"recommendation\": \"Specific collaboration strategy with implementation steps\"\n}\n</json>",
"examples": [
"Set up effective remote team collaboration",
"Improve designer-developer handoff",
"Establish AI pair programming workflow",
"Create cross-team API development process"
]
}